Why URL manipulation handles routing in Nginx - Visual Breakdown

Process Flow - Why URL manipulation handles routing

User enters URL in browser

↓

Browser sends HTTP request with URL

↓

nginx receives request

↓

nginx reads URL path

↓

nginx matches URL to routing rules

↓

nginx forwards request to correct backend or serves file

↓

Response sent back to user

The URL entered by the user guides nginx to decide which content or backend to serve by matching routing rules.

Execution Sample

Nginx

location /app1/ {
    proxy_pass http://backend1;
}

location /app2/ {
    proxy_pass http://backend2;
}

nginx uses URL paths /app1/ and /app2/ to route requests to different backend servers.

Process Table

Step	Incoming URL	nginx Action	Routing Decision	Result
1	http://example.com/app1/page	Reads URL path /app1/page	Matches location /app1/	Forwards to backend1
2	http://example.com/app2/home	Reads URL path /app2/home	Matches location /app2/	Forwards to backend2
3	http://example.com/static/image.png	Reads URL path /static/image.png	No matching location, uses default	Serves static file or 404
4	http://example.com/app3/	Reads URL path /app3/	No matching location	Uses default server block or 404

💡 Routing ends after matching URL path to location blocks or default handling.

Status Tracker

Variable	Start	After Step 1	After Step 2	After Step 3	After Step 4
URL Path	/	/app1/page	/app2/home	/static/image.png	/app3/
Routing Match	none	/app1/	/app2/	none	none
Backend or Action	none	backend1	backend2	default/static	default/404

Key Moments - 2 Insights

Why does nginx use the URL path to decide where to send the request?

Because the URL path uniquely identifies the resource or service the user wants, nginx matches it to location blocks to route correctly, as shown in steps 1 and 2 of the execution table.

What happens if the URL path does not match any location block?

nginx uses the default server block or returns a 404 error, as seen in steps 3 and 4 where no matching location is found.

Visual Quiz - 3 Questions

Look at the execution table, which backend does nginx forward to when the URL is http://example.com/app1/page?

A default server

B backend2

C backend1

D 404 error

💡 Hint

Check Step 1 in the execution table where the URL path matches /app1/ and forwards to backend1.

At which step does nginx fail to find a matching location block?

A Step 2

B Step 3

C Step 1

D Step 4

💡 Hint

Look at the Routing Decision column in the execution table for steps without matching location.

If a new location /app3/ is added to nginx config, how would the routing decision change for URL http://example.com/app3/?

A It would match /app3/ and forward accordingly

B It would forward to backend1

C It would forward to backend2

D It would still use default server block

💡 Hint

Refer to the variable_tracker and execution_table showing how matching location affects routing.

Concept Snapshot

nginx routing uses URL paths to decide request handling.
Location blocks match URL prefixes.
Matching location forwards request to backend or serves files.
No match uses default server or returns 404.
URL manipulation changes routing outcome.

Full Transcript

When a user types a URL, the browser sends a request with that URL to nginx. nginx reads the URL path and compares it to its configured location blocks. If the URL path matches a location, nginx forwards the request to the backend server or serves the content defined there. If no location matches, nginx uses the default server block or returns a 404 error. This is why changing the URL path changes where the request goes, which is called URL manipulation handling routing.