Nginx as reverse proxy in Express - Step-by-Step Execution

Concept Flow - Nginx as reverse proxy

Client sends request

↓

Nginx receives request

↓

Nginx forwards request to Express server

↓

Express server processes request

↓

Express sends response back to Nginx

↓

Nginx sends response to Client

The client sends a request to Nginx, which forwards it to the Express server. Express processes it and sends the response back through Nginx to the client.

Execution Sample

Express

server {
  listen 80;
  location / {
    proxy_pass http://localhost:3000;
  }
}

Nginx listens on port 80 and forwards all requests to the Express server running on port 3000.

Execution Table

Step	Action	Request URL	Server Handling	Response Sent
1	Client sends GET /	GET /	Nginx receives request	No response yet
2	Nginx forwards to Express	GET /	Express receives request	No response yet
3	Express processes request	GET /	Express prepares response	No response yet
4	Express sends response	GET /	Response sent to Nginx	Response data
5	Nginx sends response to client	GET /	Response forwarded	Client receives response
6	Request complete	GET /	No further action	Connection closed

💡 Request completes after Nginx sends Express response back to client

Variable Tracker

Variable	Start	After Step 2	After Step 4	Final
Request URL	GET /	GET /	GET /	GET /
Server Handling	None	Express	Express	Nginx
Response Sent	None	None	Response data	Response data

Key Moments - 3 Insights

Why does the client never connect directly to the Express server?

Because Nginx acts as a middleman (reverse proxy), forwarding requests and responses, as shown in execution_table steps 1-5.

What happens if Express server is down?

Nginx will receive no response to forward, causing errors or timeouts, since it depends on Express to handle requests (see step 3 and 4).

Why use Nginx instead of connecting client directly to Express?

Nginx can handle many tasks like load balancing, caching, and security, improving performance and reliability beyond what Express alone provides.

Visual Quiz - 3 Questions

Look at the execution_table, at which step does Express send the response back to Nginx?

A Step 3

B Step 4

C Step 2

D Step 5

💡 Hint

Check the 'Response Sent' column in execution_table row for Step 4.

According to variable_tracker, what is the value of 'Server Handling' after Step 4?

A Express

B Nginx

C Client

D None

💡 Hint

Look at the 'Server Handling' row and the 'After Step 4' column in variable_tracker.

If Nginx did not forward the request, what would the client experience?

A Immediate response from Express

B Response from Nginx cache

C No response or timeout

D Direct connection to Express

💡 Hint

Refer to key_moments about what happens if Express is down or Nginx does not forward requests.

Concept Snapshot

Nginx as reverse proxy:
- Nginx listens on a public port (e.g., 80)
- Forwards client requests to Express server (e.g., localhost:3000)
- Express processes and sends response back to Nginx
- Nginx forwards response to client
- Improves security, load balancing, and performance

Full Transcript

This visual execution shows how Nginx acts as a reverse proxy for an Express server. The client sends a request to Nginx, which forwards it to Express. Express processes the request and sends the response back to Nginx. Finally, Nginx sends the response to the client. Variables like Request URL, Server Handling, and Response Sent change step-by-step. Key moments clarify why Nginx is used and what happens if Express is down. The quiz tests understanding of the flow and variable states.