Why location matching controls request routing in Nginx - Challenge Your Understanding

Challenge - 5 Problems

🧠 Conceptual

intermediate

How does NGINX decide which location block handles a request?

NGINX uses location blocks to route requests. Which statement best explains how NGINX chooses the correct location block?

A NGINX always uses the first location block defined in the configuration regardless of the request URI.

B NGINX randomly picks any location block that contains the requested URI substring.

C NGINX matches the request URI against location blocks in order, using the first match it finds.

D NGINX selects the location block with the longest matching prefix or the best regex match for the request URI.

💡 Hint

Think about how NGINX tries to find the most specific match for a request URI.

NGINX uses a specific order to match location blocks. It first looks for exact matches, then prefix matches with the longest prefix, and finally regex matches. This ensures the most specific location handles the request.

💻 Command Output

intermediate

Which backend handles /app/v3/page?

Given this NGINX config snippet:

server {
  listen 80;
  location /app/ {
    proxy_pass http://backend1;
  }
  location /app/v2/ {
    proxy_pass http://backend2;
  }
}

What happens if a request is made to /app/v3/page?

A The request is routed to backend1 because /app/ is the longest matching prefix.

B The request is routed to backend2 because /app/v2/ is the closest match.

C NGINX returns a 404 error because no location matches /app/v3/page exactly.

D NGINX returns a 500 error due to configuration conflict.

💡 Hint

Consider prefix matching rules and which location block matches the request URI.

The request URI /app/v3/page matches the prefix /app/ but not /app/v2/. NGINX routes to the location with the longest matching prefix, which is /app/.

❓ Configuration

advanced

Which location block will handle the request?

Consider this NGINX configuration:

location /images/ {
  root /data;
}
location ~* \.(gif|jpg|jpeg)$ {
  root /images;
}

What location block handles a request for /images/cat.jpg?

A Both location blocks handle the request simultaneously.

B The second location block because the regex matches the file extension .jpg.

C The first location block because it matches the prefix /images/.

D NGINX returns a 404 error because of conflicting location blocks.

💡 Hint

Remember that regex locations have higher priority than prefix locations if they match.

NGINX first checks prefix locations, but if a regex location matches, it takes priority. Since the request URI ends with .jpg, the regex location handles it.

❓ Troubleshoot

advanced

Why does the backend receive the full URI?

An NGINX server has these location blocks:

location /api/ {
  proxy_pass http://api_backend;
}
location /api/v1/ {
  proxy_pass http://api_v1_backend;
}

A request to /api/v1/users is proxied to http://api_v1_backend/api/v1/users instead of http://api_v1_backend/users. Why?

A Because the proxy_pass directive is missing a trailing slash in /api/v1/ location.

B Because the /api/ location is defined before /api/v1/, NGINX matches it first and stops.

C Because NGINX does not support nested location blocks and ignores /api/v1/.

D Because the /api/v1/ location is a prefix but /api/ is an exact match.

💡 Hint

Check how proxy_pass handles URI rewriting with and without trailing slashes.

Without a trailing slash in proxy_pass, NGINX passes the full request URI to the upstream without stripping the location prefix. Adding a trailing slash fixes the URI rewriting for the correct backend.

✅ Best Practice

expert

What is the best way to ensure correct routing with overlapping location blocks?

You have multiple overlapping location blocks in NGINX. What is the best practice to control routing precisely?

A Place the most general location block first and rely on NGINX to pick the best match automatically.

B Define all location blocks as prefix matches without regex to avoid confusion.

C Use exact match (=) for the most specific URIs and regex (~ or ~*) for pattern matching, placing exact matches first.

D Use only regex locations to handle all routing cases for consistency.

💡 Hint

Think about how NGINX prioritizes exact, prefix, and regex locations.

Exact matches (=) have the highest priority, followed by longest prefix matches, then regex matches. Using exact matches for specific URIs and regex for patterns helps control routing clearly.

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