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

Concept Flow - Nginx as reverse proxy

Client sends HTTP request

↓

Nginx receives request

↓

Nginx forwards request to Django app

↓

Django app processes request

↓

Django app sends response back to Nginx

↓

Nginx sends response to client

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

Execution Sample

Django

server {
    listen 80;
    location / {
        proxy_pass http://127.0.0.1:8000;
    }
}

Nginx listens on port 80 and forwards all requests to the Django app running on localhost port 8000.

Execution Table

Step	Action	Request URL	Nginx Behavior	Django Response	Client Receives
1	Client sends request	/home	Receives request	No response yet	No response yet
2	Nginx forwards request	/home	Forwards to http://127.0.0.1:8000/home	Processes request	No response yet
3	Django processes	/home	Waiting for response	Generates HTML page	No response yet
4	Django sends response	/home	Receives response	Sends HTML back	No response yet
5	Nginx sends response	/home	Sends HTML to client	Response sent	Receives HTML page
6	Client renders page	/home	Idle	Idle	Page displayed
7	End	-	-	-	-

💡 Request cycle completes when client receives the response and renders the page.

Variable Tracker

Variable	Start	After Step 2	After Step 4	After Step 5	Final
Request URL	None	/home	/home	/home	/home
Nginx State	Idle	Forwarding request	Waiting for response	Sending response	Idle
Django State	Idle	Processing request	Sending response	Idle	Idle
Client State	Idle	Waiting	Waiting	Receiving response	Page displayed

Key Moments - 3 Insights

Why does Nginx forward the request instead of handling it directly?

Nginx acts as a reverse proxy to efficiently manage connections and serve static files, while Django handles the application logic. See execution_table step 2 where Nginx forwards the request to Django.

When does the client actually receive the response?

The client receives the response only after Django processes it and Nginx sends it back, as shown in execution_table step 5.

What happens if Django is not running on port 8000?

Nginx will fail to forward the request, causing errors or timeouts. This is because proxy_pass points to http://127.0.0.1:8000, so Django must be listening there.

Visual Quiz - 3 Questions

Look at the execution_table, what is Nginx doing at step 3?

A Forwarding the request to Django

B Sending response to client

C Waiting for Django's response

D Idle

💡 Hint

Check the 'Nginx Behavior' column at step 3 in the execution_table.

At which step does the client receive the HTML page?

A Step 5

B Step 4

C Step 2

D Step 3

💡 Hint

Look at the 'Client Receives' column in the execution_table.

If Django was listening on port 9000 instead of 8000, what would change in the execution_table?

A Client would receive response earlier

B Nginx would forward to port 9000 instead of 8000

C No change needed in Nginx config

D Django would not process requests

💡 Hint

Check the proxy_pass URL in the execution_sample code and relate to step 2 in execution_table.

Concept Snapshot

Nginx as reverse proxy:
- Nginx listens on a public port (e.g., 80)
- Forwards client requests to Django app (e.g., localhost:8000)
- Django processes and returns response
- Nginx sends response back to client
- Improves performance and security by separating concerns

Full Transcript

This visual trace shows how Nginx acts as a reverse proxy for a Django application. The client sends an HTTP request to Nginx, which listens on port 80. Nginx forwards the request to the Django app running on localhost port 8000. Django processes the request and sends back a response. Nginx then sends this response to the client, which renders the page. Variables like request URL and states of Nginx, Django, and client change step-by-step. Key moments include understanding why Nginx forwards requests, when the client receives the response, and the importance of correct port configuration. The quiz tests understanding of Nginx's role at different steps and configuration impact.