Why advanced patterns solve complex requirements in Nginx - See It in Action

Why advanced patterns solve complex requirements

📖 Scenario: You are managing a busy website that needs to handle different types of requests efficiently. Some requests need special treatment, like redirecting users based on their location or blocking bad traffic. Simple rules are not enough, so you want to use advanced nginx patterns to solve these complex needs.

🎯 Goal: Build an nginx configuration that uses advanced patterns like regular expressions and conditional blocks to route requests differently based on URL paths and user IP addresses.

📋 What You'll Learn

Create a server block listening on port 80

Use a variable $blocked_ips containing a list of IPs to block

Use map directive to set a variable $is_blocked based on $remote_addr

Use location blocks with regex to match URLs starting with /api/ and /admin/

Use if condition to return 403 Forbidden for blocked IPs

Use return directives to redirect or serve content based on conditions

💡 Why This Matters

🌍 Real World

Web servers often need to handle many types of requests and block bad traffic. Using advanced nginx patterns helps manage complex routing and security rules efficiently.

💼 Career

Understanding advanced nginx configuration is important for DevOps engineers and system administrators to secure and optimize web services.

1

Create the initial server block

Create an nginx server block that listens on port 80 and has a root directory set to /var/www/html.

Nginx

server {
    listen 80;
    root /var/www/html;
    # Your code here
}

Hint

Use server {} block with listen 80; and root /var/www/html; inside.

2

Add blocked IPs list and map variable

Add a variable $blocked_ips with the value "192.168.1.10 10.0.0.5". Then use the map directive to create a variable $is_blocked that is 1 if $remote_addr matches any IP in $blocked_ips, otherwise 0.

Nginx

server {
    listen 80;
    root /var/www/html;
}

# Your code here

Hint

Use map $remote_addr $is_blocked { ... } outside the server block to set $is_blocked.

3

Add location blocks with regex and blocking logic

Inside the server block, add two location blocks: one matching URLs starting with /api/ using regex ~ ^/api/, and another matching URLs starting with /admin/ using regex ~ ^/admin/. Inside the server block, add an if condition that returns 403 Forbidden if $is_blocked equals 1.

Nginx

server {
    listen 80;
    root /var/www/html;

    # Your code here
}

map $remote_addr $is_blocked {
    default 0;
    192.168.1.10 1;
    10.0.0.5 1;
}

Hint

Use if ($is_blocked = 1) { return 403; } inside server. Use regex location ~ ^/api/ {} and location ~ ^/admin/ {}.

4

Add redirects and print final configuration

Inside the /admin/ location block, add a return 302 directive to redirect requests to /login. Then add a location / block that returns a simple HTML page with text Welcome to the homepage. Finally, print the entire nginx configuration file content.

Nginx

server {
    listen 80;
    root /var/www/html;

    if ($is_blocked = 1) {
        return 403;
    }

    location ~ ^/api/ {
        proxy_pass http://backend_api;
    }

    location ~ ^/admin/ {
        proxy_pass http://admin_panel;
        # Your code here
    }

    # Your code here
}

map $remote_addr $is_blocked {
    default 0;
    192.168.1.10 1;
    10.0.0.5 1;
}

Hint

Use return 302 /login; inside /admin/ location. Add location / { return 200 '...'; } for homepage. Print full config.

Practice

1. What is the main benefit of using advanced nginx patterns in server configuration?

easy

A. They allow handling complex routing and conditional responses.

B. They reduce the server's memory usage significantly.

C. They automatically update nginx to the latest version.

D. They simplify the installation process of nginx.

Solution

1. Step 1: Understand nginx pattern purpose

   Advanced patterns in nginx help manage complex routing and conditions for requests.

2. Step 2: Compare options

   Only They allow handling complex routing and conditional responses. correctly states the benefit of handling complex routing and conditional responses.

3. Final Answer:

   They allow handling complex routing and conditional responses. -> Option A

4. Quick Check:

   Advanced patterns = complex routing [OK]

Hint: Advanced patterns handle complex routes and conditions [OK]

Common Mistakes:

• Confusing performance improvements with routing benefits
• Thinking nginx auto-updates with patterns
• Assuming patterns simplify installation

2. Which of the following is a correct nginx directive syntax to match requests only for the domain example.com?

easy

A. server_name = example.com;

B. server_name example.com;

C. server_name ~ example.com;

D. server_name !example.com;

Solution

1. Step 1: Recall server_name directive syntax

   The correct syntax to specify a domain is server_name example.com; without extra symbols.

2. Step 2: Analyze other options

   Options B, C, and D use invalid or unsupported syntax for server_name.

3. Final Answer:

   server_name example.com; -> Option B

4. Quick Check:

   Correct server_name syntax = server_name example.com; [OK]

Hint: Use plain domain name without symbols for server_name [OK]

Common Mistakes:

• Adding unsupported symbols like = or ~
• Using negation symbol ! which is invalid
• Confusing regex with server_name syntax

3. Given this nginx config snippet:

location /api/ {
  if ($request_method = POST) {
    return 405;
  }
  proxy_pass http://backend;
}

What happens when a POST request is sent to /api/data?

medium

A. The server returns HTTP status 405 Method Not Allowed.

B. The request is proxied to http://backend.

C. The request is redirected to /api/ with GET method.

D. The server returns HTTP status 404 Not Found.

Solution

1. Step 1: Analyze the if condition

   The config checks if the request method is POST and returns 405 if true.

2. Step 2: Apply condition to POST request

   Since the request is POST, nginx returns 405 and does not proxy the request.

3. Final Answer:

   The server returns HTTP status 405 Method Not Allowed. -> Option A

4. Quick Check:

   POST request triggers 405 return [OK]

Hint: If condition returns 405 on POST, request won't proxy [OK]

Common Mistakes:

• Assuming proxy_pass always runs regardless of if
• Confusing 405 with 404 status codes
• Thinking request is redirected instead of blocked

4. You wrote this nginx config to redirect HTTP to HTTPS:

server {
  listen 80;
  server_name example.com;
  return 301 https://$server_name$request_uri;
}

But the redirect does not work. What is the likely error?

medium

A. The server block must listen on port 443 for redirects.

B. Missing semicolon after listen 80 directive.

C. Using $server_name instead of $host in the return statement.

D. Incorrect HTTP status code; should be 302 instead of 301.

Solution

1. Step 1: Understand variable usage in redirect

   $server_name may not hold the requested host; $host is preferred for redirects.

2. Step 2: Check other options

   Semicolon is present, 301 is correct for permanent redirect, and listening on 80 is correct for HTTP to HTTPS redirect.

3. Final Answer:

   Using $server_name instead of $host in the return statement. -> Option C

4. Quick Check:

   Use $host for redirects, not $server_name [OK]

Hint: Use $host, not $server_name, for redirect URLs [OK]

Common Mistakes:

• Confusing $server_name with $host variable
• Thinking 301 is wrong status code for redirect
• Believing listen 443 is needed for HTTP to HTTPS redirect

5. You want nginx to serve static files from /var/www/static only if the request URI starts with /static/, otherwise proxy to backend. Which config snippet correctly implements this advanced pattern?

hard

A. location /static/ {
root /var/www/static;
}
location / {
proxy_pass http://backend;
}

B. location / {
proxy_pass http://backend;
}
location /static/ {
root /var/www/static;
}

C. location /static/ {
proxy_pass http://backend;
}
location / {
root /var/www/static;
}

D. location /static/ {
alias /var/www/static/;
}
location / {
proxy_pass http://backend;
}

Solution

1. Step 1: Understand root vs alias for static files

   Using alias with full path is correct for serving static files from a subdirectory.

2. Step 2: Check location order and proxy

   Requests starting with /static/ serve files from /var/www/static/, others proxy to backend.

3. Final Answer:

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

4. Quick Check:

   Use alias for static path, proxy others [OK]

Hint: Use alias for static folder, proxy others [OK]

Common Mistakes:

• Using root instead of alias causing wrong file paths
• Reversing location blocks order
• Proxying static requests instead of serving files