Historic Atlas / EngineeringREQUEST ROUTING LAB ↗
INGRESS / ARCHITECTURE NOTE

One origin.
Clear routes.

nginx · Unprivileged listener · :8080

A deliberately small edge for the atlas. Terminate TLS in front, route by path, and leave authentication where it belongs: in the backend.

Interactive documentation, not a live infrastructure console.

BrowserSingle public origin
TLS terminated upstream
→
nginxDocker DNS per request
Session credentials forwarded
→
backend/api/ · gated /actuator/
keycloakPublic /auth/ endpoints
frontendEverything else · /health
FOLLOW A REQUEST

Where does this path go?

Change the inputs to inspect a local policy specimen.

POLICY RESULT / NO REQUEST SENT

Forwarded scheme / host

X-Request-Id

ILLUSTRATIVE ACCESS LOG

Status and durations below are example values, not measured responses. Cookies and authorization headers are never included.

BOUNDARY / 01

Route, don't authenticate.

Session credentials pass through unchanged. The backend validates every non-public request; ingress is not an authorization layer. Keycloak routes retain their prefix and use the separate authentication specification's endpoint allowlist.

BOUNDARY / 02

Public edge. Private metrics.

The public listener is 8080. A separate, unpublished 8081 listener exposes stub_status to the Compose exporter. Public /metrics is not a route to that private listener. /health goes to the frontend.

BOUNDARY / 03

A small, reproducible image.

Paketo's nginx buildpack packages nginx.conf in avarc-server-ingress. Docker's resolver refreshes upstream lookup per request. Error logs remain plain text on stderr. Caching, compression and rate limits are open decisions.

This page visualizes the supplied nginx policy. It does not configure a proxy, inspect a network, validate a deployment or generate real access logs. The request-ID generator is a local specimen, not nginx's implementation.