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.