Why URL manipulation handles routing in Nginx - Challenge Your Understanding

Challenge - 5 Problems

🧠 Conceptual

intermediate

How does URL manipulation affect routing in nginx?

In nginx, what is the main reason URL manipulation is used to handle routing?

A It allows nginx to decide which backend server or resource to serve based on the URL path.

B It compresses the URL to reduce bandwidth usage.

C It encrypts the URL to secure the connection between client and server.

D It changes the URL to a random string to prevent caching.

💡 Hint

Think about how nginx uses the URL path to find the right content or service.

nginx uses the URL path to route requests to the correct backend or serve the right file. Manipulating the URL helps it match patterns and decide where to send the request.

💻 Command Output

intermediate

What is the output of this nginx rewrite rule?

Given this nginx configuration snippet:

location /app/ {
  rewrite ^/app/(.*)$ /$1 break;
}

What will be the rewritten URL when a client requests /app/dashboard?

Nginx

location /app/ {
  rewrite ^/app/(.*)$ /$1 break;
}

A /dashboard

B /app//dashboard

C /app/dashboard

D /app

💡 Hint

Look at the rewrite regex and what it captures.

The rewrite rule captures everything after '/app/' and rewrites the URL to '/' plus the captured part. So '/app/dashboard' becomes '/dashboard'.

❓ Configuration

advanced

Which nginx config correctly routes URLs with query strings?

You want nginx to route requests starting with /search to a backend server, preserving the query string. Which configuration snippet does this correctly?

A

location /search {
  proxy_pass http://backend/search?query=$args;
}

B

location /search {
  proxy_pass http://backend/search;
}

C

location /search {
  proxy_pass http://backend/search?$args;
}

D

location /search {
  proxy_pass http://backend/search$is_args$args;
}

💡 Hint

Remember how nginx appends query strings with $is_args and $args.

Option D uses $is_args which adds '?' if there are arguments, and $args to append the original query string, preserving it correctly.

❓ Troubleshoot

advanced

Why does this nginx rewrite cause a redirect loop?

Consider this nginx config:

location /old/ {
  rewrite ^/old/(.*)$ /new/$1 permanent;
}
location /new/ {
  rewrite ^/new/(.*)$ /old/$1 permanent;
}

What is the cause of the redirect loop?

A nginx does not support rewrite rules inside location blocks.

B Both locations rewrite URLs to each other permanently, causing infinite redirects.

C The 'permanent' flag is missing in one rewrite causing mismatch.

D The regex patterns are invalid and cause nginx to crash.

💡 Hint

Think about what happens when a URL matches /old/ and then /new/ repeatedly.

Each rewrite sends the URL to the other location with a permanent redirect, causing the browser to bounce back and forth endlessly.

✅ Best Practice

expert

What is the best practice for handling trailing slashes in nginx routing?

You want to ensure URLs with or without trailing slashes are routed consistently to avoid duplicate content. Which nginx configuration snippet follows best practice?

A

location /app {
  try_files $uri $uri/ =404;
}

B

location /app/ {
  rewrite ^/(.*)/$ /$1 permanent;
}

C

location /app/ {
  rewrite ^/(.*[^/])$ /$1/ permanent;
}

D

location /app {
  rewrite ^/(.*)/$ /$1/ permanent;
}

💡 Hint

Consider how to redirect URLs without trailing slash to ones with trailing slash.

Option C redirects URLs missing a trailing slash to the same URL with a trailing slash, ensuring consistent URL format and avoiding duplicate content.