Nginx as reverse proxy in Django - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to specify the port Nginx listens on.

Django

server {
    listen [1];
    location / {
        proxy_pass http://127.0.0.1:8000;
    }
}

Drag options to blanks, or click blank then click option'

A80

B443

C22

D8080

Attempts:

3 left

💡 Hint

Common Mistakes

Using port 443 without SSL configuration

Using SSH port 22 by mistake

The listen directive tells Nginx which port to listen on. Port 80 is the default for HTTP.

2fill in blank

medium

Complete the code to set the proxy header for the original host.

Django

location / {
    proxy_set_header Host [1];
    proxy_pass http://127.0.0.1:8000;
}

Drag options to blanks, or click blank then click option'

A$remote_addr

B$host

C$http_user_agent

D$server_name

Attempts:

3 left

💡 Hint

Common Mistakes

Using $remote_addr instead of $host

Using $server_name which is the server's own name

The proxy_set_header Host $host; passes the original host header to the backend server.

3fill in blank

hard

Fix the error in the proxy_pass URL to correctly forward requests to Django.

Django

location / {
    proxy_pass http://127.0.0.1[1]8000;
}

Drag options to blanks, or click blank then click option'

A:

B//

C/

D;

Attempts:

3 left

💡 Hint

Common Mistakes

Using slash instead of colon before port

Adding extra slashes causing malformed URL

The proxy_pass URL must have a colon before the port number, like http://127.0.0.1:8000.

4fill in blank

hard

Fill both blanks to set headers for real IP and forwarded protocol.

Django

location / {
    proxy_set_header X-Real-IP [1];
    proxy_set_header X-Forwarded-Proto [2];
    proxy_pass http://127.0.0.1:8000;
}

Drag options to blanks, or click blank then click option'

A$remote_addr

B$host

C$scheme

D$server_name

Attempts:

3 left

💡 Hint

Common Mistakes

Using $host for X-Real-IP

Using $host instead of $scheme for X-Forwarded-Proto

X-Real-IP should be set to $remote_addr to pass the client's IP. X-Forwarded-Proto uses $scheme to indicate HTTP or HTTPS.

5fill in blank

hard

Fill all three blanks to correctly configure proxy headers for Django behind Nginx.

Django

location / {
    proxy_set_header Host [1];
    proxy_set_header X-Real-IP [2];
    proxy_set_header X-Forwarded-For [3];
    proxy_pass http://127.0.0.1:8000;
}

Drag options to blanks, or click blank then click option'

A$host

B$remote_addr

C$proxy_add_x_forwarded_for

D$server_name

Attempts:

3 left

💡 Hint

Common Mistakes

Using $server_name instead of $host

Not using $proxy_add_x_forwarded_for for X-Forwarded-For

These headers ensure Django receives the original host, client IP, and the chain of forwarded IPs.

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