Why Nginx handles API routing - Visual Breakdown

Process Flow - Why Nginx handles API routing

Client sends API request

↓

Nginx receives request

↓

Check request URL path

Yes No↓

Forward to API server

↓

API server processes request

↓

Response sent back through Nginx

↓

Client receives API response

Nginx receives client requests, checks if the URL path matches API routes, forwards API requests to the API server, and returns the response to the client.

Execution Sample

Nginx

location /api/ {
    proxy_pass http://api_backend;
}

This Nginx config routes all requests starting with /api/ to the API backend server.

Process Table

Step	Request URL	Nginx Action	Routing Decision	Result
1	/api/users	Check URL path	Matches /api/	Forward to API backend
2	/api/users	Proxy request	Send to http://api_backend	API server processes
3	/api/users	Receive response	From API backend	Send response to client
4	/index.html	Check URL path	Does not match /api/	Serve static file
5	/index.html	Serve file	Static content	Send file to client

💡 Requests not matching /api/ are served as static files; /api/ requests are proxied to API backend.

Status Tracker

Variable	Start	After Step 1	After Step 2	After Step 3	Final
Request URL	N/A	/api/users	/api/users	/api/users	Response sent
Routing Decision	N/A	Matches /api/	Forwarded	Response received	Completed
Response	N/A	N/A	Pending	Received from API	Sent to client

Key Moments - 3 Insights

Why does Nginx check the URL path before forwarding?

Nginx uses the URL path to decide if the request is for the API or for static content. This is shown in execution_table step 1 where the URL is checked to match /api/.

What happens if the URL does not start with /api/?

Nginx serves the request as static content or other configured content, as seen in execution_table step 4 and 5.

How does Nginx forward the API request to the backend?

Nginx uses proxy_pass to send the request to the API backend server, shown in execution_table step 2.

Visual Quiz - 3 Questions

Look at the execution table, what is the routing decision at step 1 for URL /api/users?

A Matches /api/, forward to API backend

B Does not match /api/, serve static file

C Send error response

D Ignore request

💡 Hint

Check the 'Routing Decision' column in row for step 1.

At which step does Nginx send the API response back to the client?

A Step 2

B Step 4

C Step 3

D Step 5

💡 Hint

Look at the 'Result' column for when response is sent to client.

If the request URL is /home, what would Nginx do according to the execution table?

A Forward to API backend

B Serve static file

C Return 404 error

D Proxy to another server

💡 Hint

See steps 4 and 5 for requests not matching /api/.

Concept Snapshot

Nginx routes API requests by matching URL paths.
Use 'location /api/' block to proxy API calls.
Requests matching /api/ go to backend server.
Others serve static files or default content.
This improves performance and organization.

Full Transcript

When a client sends a request, Nginx first checks the URL path. If the path starts with /api/, Nginx forwards the request to the API backend server using proxy_pass. The API server processes the request and sends the response back through Nginx to the client. If the URL does not start with /api/, Nginx serves static files or other content directly. This routing helps separate API traffic from static content efficiently.