Nginx as reverse proxy in Django - Cheat Sheet & Quick Revision

Recall & Review

beginner

What is a reverse proxy in the context of web servers?

A reverse proxy is a server that sits between clients and web servers. It receives client requests and forwards them to backend servers, then sends the server's response back to the client. It helps with load balancing, security, and caching.

beginner

Why use Nginx as a reverse proxy for a Django application?

Nginx can handle many client connections efficiently, serve static files quickly, and forward dynamic requests to Django's application server. This improves performance, security, and scalability.

intermediate

Which Nginx directive is used to forward requests to the Django backend?

The proxy_pass directive is used in Nginx to forward client requests to the Django backend server, such as Gunicorn or uWSGI.

beginner

How does Nginx improve serving static files for Django apps?

Nginx can serve static files like images, CSS, and JavaScript directly without involving Django. This reduces load on Django and speeds up response times.

intermediate

What is the role of the location block in Nginx configuration for Django?

The location block defines how Nginx handles requests for specific URL paths. For example, it can route static files to Nginx and dynamic requests to Django's backend.

What does Nginx do when acting as a reverse proxy for Django?

A Replaces Django as the web framework

B Runs Django application code directly

C Only serves static files without forwarding

D Forwards client requests to Django and returns responses

Nginx forwards client requests to the Django backend and returns the responses to clients.

Which directive in Nginx config forwards requests to Django's Gunicorn server?

A root

B proxy_pass

C listen

D server_name

The proxy_pass directive forwards requests to the backend server like Gunicorn.

Why is it better for Nginx to serve static files instead of Django?

A Nginx is faster and reduces load on Django

B Django cannot serve static files

C Static files are not needed in Django apps

D Nginx compresses static files automatically

Nginx is optimized to serve static files quickly, which reduces the work Django has to do.

What is the purpose of the location block in Nginx?

A To install Nginx modules

B To start the Django server

C To define how requests for certain URLs are handled

D To configure database connections

The location block tells Nginx how to handle requests matching specific URL patterns.

Which of these is NOT a benefit of using Nginx as a reverse proxy?

A Running Django ORM queries

B Improved security

C Load balancing

D Caching responses

Running Django ORM queries is done by Django, not Nginx.

Explain how Nginx acts as a reverse proxy for a Django application and why this setup is useful.

Think about how Nginx handles different types of requests and helps Django.

Describe the key parts of an Nginx configuration file that enable it to reverse proxy to Django.

Focus on how Nginx routes requests and serves files.

Practice

1. What is the main role of Nginx when used as a reverse proxy for a Django application?

easy

A. Replace the Django application with a static website

B. Directly execute Django Python code

C. Forward client requests to the Django application server

D. Store the Django database backups

Solution

1. Step 1: Understand Nginx reverse proxy function

   Nginx acts as a middleman that receives client requests and forwards them to the Django app server.

2. Step 2: Identify what Nginx does not do

   Nginx does not replace Django, execute Python code, or store backups; it only forwards requests and can serve static files.

3. Final Answer:

   Forward client requests to the Django application server -> Option C

4. Quick Check:

   Nginx forwards requests [OK]

Hint: Nginx forwards requests to Django, it doesn't run Django code [OK]

Common Mistakes:

• Thinking Nginx runs Django code
• Confusing Nginx with a database
• Assuming Nginx replaces Django app

2. Which Nginx configuration snippet correctly sets it as a reverse proxy forwarding requests to a Django app running on port 8000?

easy

A. location / { proxy_pass http://127.0.0.1:8000; }

B. location / { root /var/www/html; }

C. location / { fastcgi_pass 127.0.0.1:8000; }

D. location / { proxy_redirect off; }

Solution

1. Step 1: Identify correct proxy directive

   To forward requests, Nginx uses proxy_pass with the Django app address and port.

2. Step 2: Check other options for correctness

   root serves static files, fastcgi_pass is for FastCGI apps, and proxy_redirect controls redirects but doesn't forward requests.

3. Final Answer:

   location / { proxy_pass http://127.0.0.1:8000; } -> Option A

4. Quick Check:

   Use proxy_pass for reverse proxy [OK]

Hint: proxy_pass forwards requests to backend server [OK]

Common Mistakes:

• Using root instead of proxy_pass for proxying
• Confusing fastcgi_pass with proxy_pass
• Omitting the backend address in proxy_pass

3. Given this Nginx config snippet, what happens when a client requests /static/css/style.css?

location /static/ {
    alias /home/user/myproject/static/;
}
location / {
    proxy_pass http://127.0.0.1:8000;
}

medium

A. Nginx serves the static file directly from /home/user/myproject/static/css/style.css

B. Nginx forwards the request to Django app on port 8000

C. Nginx returns a 404 error because alias is incorrect

D. Nginx redirects the request to /static/css/style.css on Django

Solution

1. Step 1: Understand alias directive for static files

   The location /static/ block uses alias to serve files directly from the filesystem path.

2. Step 2: Analyze request routing

   Requests to /static/ are served by Nginx from the alias path; other requests go to Django via proxy_pass.

3. Final Answer:

   Nginx serves the static file directly from /home/user/myproject/static/css/style.css -> Option A

4. Quick Check:

   Static files served by alias [OK]

Hint: alias serves static files directly, proxy_pass forwards others [OK]

Common Mistakes:

• Thinking all requests go to Django
• Confusing alias with root directive
• Assuming Nginx redirects instead of serving static files

4. You configured Nginx as a reverse proxy for Django but get a 502 Bad Gateway error. Which fix is most likely correct?

medium

A. Change Nginx config to use root instead of proxy_pass

B. Start the Django app server on the port Nginx proxies to

C. Remove the location block for static files

D. Disable firewall on the client machine

Solution

1. Step 1: Understand 502 Bad Gateway cause

   502 means Nginx cannot connect to the backend server, often because it is not running or listening on the expected port.

2. Step 2: Identify the correct fix

   Starting the Django app server on the port Nginx expects resolves the connection issue.

3. Final Answer:

   Start the Django app server on the port Nginx proxies to -> Option B

4. Quick Check:

   502 error means backend not reachable [OK]

Hint: 502 means backend server not running or unreachable [OK]

Common Mistakes:

• Changing root instead of fixing backend server
• Removing static files block unrelated to 502
• Disabling client firewall won't fix server connection

5. You want Nginx to serve static files directly and forward all other requests to Django on port 8000. Which combined Nginx config snippet achieves this correctly?

hard

A. location /static/ { proxy_pass http://127.0.0.1:8000; } location / { alias /var/www/myproject/static/; }

B. location / { alias /var/www/myproject/static/; } location /static/ { proxy_pass http://127.0.0.1:8000; }

C. location /static/ { root /var/www/myproject/static/; } location / { proxy_redirect http://127.0.0.1:8000; }

D. location /static/ { alias /var/www/myproject/static/; } location / { proxy_pass http://127.0.0.1:8000; }

Solution

1. Step 1: Serve static files with alias

   The location /static/ block uses alias to serve static files from the filesystem path.

2. Step 2: Forward other requests with proxy_pass

   The location / block forwards all other requests to Django running on port 8000 using proxy_pass.

3. Final Answer:

   location /static/ { alias /var/www/myproject/static/; } location / { proxy_pass http://127.0.0.1:8000; } -> Option D

4. Quick Check:

   Static files alias + proxy_pass for others [OK]

Hint: Use alias for static, proxy_pass for app requests [OK]

Common Mistakes:

• Swapping alias and proxy_pass locations
• Using proxy_redirect instead of proxy_pass
• Using root instead of alias causing path issues