Why location matching controls request routing in Nginx - See It in Action

Why location matching controls request routing in nginx

📖 Scenario: You are setting up a simple web server using nginx. You want to control how different web requests are handled based on the URL path. This is important because nginx uses location blocks to decide where to send each request.

🎯 Goal: Learn how to create location blocks in nginx configuration to control request routing based on URL paths.

📋 What You'll Learn

Create an nginx configuration file with a server block

Add a root directory for serving files

Add two location blocks for different URL paths

Print the final nginx configuration to verify the routing setup

💡 Why This Matters

🌍 Real World

Web servers like nginx use location matching to decide how to handle different web requests. This helps serve static files, proxy to backend apps, or block unwanted requests.

💼 Career

Understanding nginx location matching is essential for DevOps roles managing web servers, load balancers, and application delivery.

1

Create the basic nginx server block

Create an nginx configuration with a server block that listens on port 80 and sets the root directory to /var/www/html.

Nginx

# Your code here
# Create a server block listening on port 80 with root /var/www/html

Hint

Use server { ... } to define the server. Inside, use listen 80; and root /var/www/html;.

2

Add a location block for the root URL

Inside the server block, add a location / block that serves files from the root directory.

Nginx

server {
    listen 80;
    root /var/www/html;
    # Add a location block for / here
}

Hint

The location / block matches all requests starting with /. Use try_files $uri $uri/ =404; to serve files or show 404 if not found.

3

Add a location block for /images path

Inside the server block, add a location /images/ block that serves files from /var/www/images directory.

Nginx

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

    location / {
        try_files $uri $uri/ =404;
    }
    # Add a location block for /images/ here
}

Hint

The location /images/ block matches URLs starting with /images/. Use root /var/www; so that nginx looks for files in /var/www/images.

4

Print the final nginx configuration

Print the entire nginx configuration to verify the location blocks and routing setup.

Nginx

# Print the nginx configuration below
# Your code here

Hint

Use a print statement to display the full nginx configuration exactly as written.

Practice

1. What does the location directive in nginx control?

easy

A. How nginx routes incoming requests based on URL patterns

B. The server's IP address configuration

C. The database connection settings

D. The logging format for errors

Solution

1. Step 1: Understand the role of location in nginx

   The location directive defines how nginx matches URLs to decide where to send requests.

2. Step 2: Identify what location controls

   It controls routing of requests, not server IP, database, or logging.

3. Final Answer:

   How nginx routes incoming requests based on URL patterns -> Option A

4. Quick Check:

   Location controls routing = B [OK]

Hint: Location matches URLs to route requests [OK]

Common Mistakes:

• Confusing location with server IP settings
• Thinking location controls database connections
• Assuming location affects logging formats

2. Which of the following is the correct syntax to define a prefix location block in nginx?

easy

A. location ~ /example { }

B. location = /example { }

C. location /example { }

D. location ! /example { }

Solution

1. Step 1: Review nginx location syntax

   Prefix locations use location /path { } without modifiers.

2. Step 2: Identify correct prefix syntax

   location /example { } is correct for prefix matching.

3. Final Answer:

   location /example { } -> Option C

4. Quick Check:

   Prefix location syntax = A [OK]

Hint: Prefix location has no modifier, just path [OK]

Common Mistakes:

• Using '=' which means exact match, not prefix
• Using '~' which means regex match
• Using '!' which is invalid syntax

3. Given this nginx config snippet:

location /images/ {
  root /data;
}
location /images/thumbnails/ {
  root /thumbs;
}

Which root directory will nginx use for the request /images/thumbnails/pic.jpg?

medium

A. Default root directory

B. /data

C. Both /data and /thumbs

D. /thumbs

Solution

1. Step 1: Understand location matching order

   nginx chooses the most specific matching location block for the URL.

2. Step 2: Compare matching locations for /images/thumbnails/pic.jpg

   Both /images/ and /images/thumbnails/ match, but /images/thumbnails/ is more specific.

3. Final Answer:

   /thumbs -> Option D

4. Quick Check:

   Most specific location wins = A [OK]

Hint: Longest matching prefix location is chosen [OK]

Common Mistakes:

• Choosing the first matching location instead of the most specific
• Assuming both roots apply simultaneously
• Ignoring location specificity

4. You have these location blocks:

location /app/ {
  proxy_pass http://backend1;
}
location ~ /app/ {
  proxy_pass http://backend2;
}

Requests to /app/test always go to backend1. Why?

medium

A. Requests to /app/test do not match either location

B. Prefix locations have higher priority than regex locations

C. The config has a syntax error

D. Regex locations always override prefix locations

Solution

1. Step 1: Recall nginx location matching priority

   nginx first matches prefix locations, then regex locations only if no prefix matches.

2. Step 2: Analyze given config

   Since /app/ prefix matches /app/test, nginx uses that before regex ~ /app/.

3. Final Answer:

   Prefix locations have higher priority than regex locations -> Option B

4. Quick Check:

   Prefix beats regex if prefix matches = D [OK]

Hint: Prefix location matches first, regex only if no prefix match [OK]

Common Mistakes:

• Thinking regex always overrides prefix
• Assuming syntax error causes this
• Believing request doesn't match any location

5. You want requests to /api/v1/ to go to backend_v1 and requests to /api/ to go to backend_default. Which config correctly routes requests?

hard

A. location /api/v1/ { proxy_pass http://backend_v1; } location /api/ { proxy_pass http://backend_default; }

B. location ~ /api/ { proxy_pass http://backend_v1; } location /api/ { proxy_pass http://backend_default; }

C. location /api/ { proxy_pass http://backend_default; } location ~ /api/v1/ { proxy_pass http://backend_v1; }

D. location = /api/v1/ { proxy_pass http://backend_v1; } location /api/ { proxy_pass http://backend_default; }

Solution

1. Step 1: Understand location matching order

   nginx chooses the most specific prefix location for a request.

2. Step 2: Use more specific prefix /api/v1/

   Since /api/v1/ is longer/more specific than /api/, nginx selects it for matching requests.

3. Step 3: Check options

   location /api/v1/ { proxy_pass http://backend_v1; } location /api/ { proxy_pass http://backend_default; } uses prefix locations where the longer one wins, correctly routing requests.

4. Final Answer:

   location /api/v1/ { proxy_pass http://backend_v1; } location /api/ { proxy_pass http://backend_default; } -> Option A

5. Quick Check:

   Specific location before general = C [OK]

Hint: Place more specific location before general prefix [OK]

Common Mistakes:

• Placing general location before specific causing wrong routing
• Using regex unnecessarily for simple prefix matching
• Using exact match which only matches exact URL