Trailing slash normalization in Nginx - Cheat Sheet & Quick Revision

Recall & Review

beginner

What is trailing slash normalization in web servers?

Trailing slash normalization means making sure URLs either always end with a slash or never do, to keep URLs consistent and avoid duplicate content.

beginner

Why normalize trailing slashes in URLs?

To improve SEO by avoiding duplicate content and to ensure consistent URL handling by the server and browsers.

intermediate

How do you redirect URLs without trailing slash to ones with trailing slash in nginx?

Use a rewrite rule like:

rewrite ^([^.]*[^/])$ $1/ permanent;

This adds a slash at the end if missing.

intermediate

What does the nginx directive try_files $uri $uri/ =404; do related to trailing slashes?

It tries to serve the exact URI first, then the URI with a trailing slash, and returns 404 if neither exists. Helps handle directories and files properly.

intermediate

What is the difference between a 301 and 302 redirect in trailing slash normalization?

301 is a permanent redirect telling browsers and search engines the URL changed permanently. 302 is temporary. Use 301 for trailing slash normalization to keep SEO benefits.

Which nginx directive is commonly used to add a trailing slash to URLs missing it?

A root /var/www/html;

B proxy_pass http://backend;

C listen 80;

D rewrite ^([^.]*[^/])$ $1/ permanent;

The rewrite directive with that regex adds a trailing slash permanently.

What status code should you use for permanent trailing slash redirects?

A 200

B 301

C 302

D 404

301 means permanent redirect, which is best for SEO and trailing slash normalization.

What does the following nginx config do?

try_files $uri $uri/ =404;

A Blocks all requests

B Always redirects to homepage

C Tries file, then directory, else 404

D Enables gzip compression

It tries to serve the exact file, then the directory with slash, else returns 404.

Why avoid having both /page and /page/ accessible on your site?

A It causes duplicate content issues for SEO

B It confuses users

C It slows down the server

D It breaks HTTPS

Duplicate content can hurt SEO rankings, so normalize URLs to one form.

Which is true about trailing slash normalization?

A It ensures consistent URL format

B It only applies to image files

C It disables caching

D It requires changing DNS settings

Normalization makes URLs consistent, improving user experience and SEO.

Explain how to configure nginx to redirect URLs without trailing slashes to ones with trailing slashes.

Think about using rewrite with a regex and permanent flag.

Describe why trailing slash normalization is important for websites and SEO.

Consider how search engines treat URLs with and without slashes.

Practice

1. What is the main purpose of trailing slash normalization in nginx?

easy

A. To disable URL rewriting completely

B. To block all URLs that end with a slash

C. To serve different content based on trailing slash presence

D. To ensure URLs are consistent by adding or removing trailing slashes

Solution

1. Step 1: Understand URL consistency

   Trailing slash normalization makes URLs uniform by either adding or removing the slash at the end.

2. Step 2: Identify nginx role

   nginx uses redirects to enforce this consistency, improving user experience and SEO.

3. Final Answer:

   To ensure URLs are consistent by adding or removing trailing slashes -> Option D

4. Quick Check:

   Trailing slash normalization = URL consistency [OK]

Hint: Normalization means making URLs uniform with or without slash [OK]

Common Mistakes:

• Thinking it blocks URLs ending with slash
• Confusing normalization with disabling rewriting
• Assuming different content is served based on slash

2. Which nginx directive is used to redirect URLs for trailing slash normalization?

easy

A. proxy_pass

B. return 301

C. listen

D. root

Solution

1. Step 1: Identify redirect directive

   nginx uses return 301 to send permanent redirects for URL changes.

2. Step 2: Confirm other directives' roles

   proxy_pass forwards requests, listen sets ports, root sets file paths, none redirect URLs.

3. Final Answer:

   return 301 -> Option B

4. Quick Check:

   Redirect = return 301 [OK]

Hint: Redirects use 'return 301' in nginx config [OK]

Common Mistakes:

• Using proxy_pass for redirects
• Confusing listen with redirect
• Using root directive incorrectly

3. Given this nginx snippet, what happens when a user visits /example/?

location /example {
  if ($request_uri ~ ".+/$") {
    return 301 $scheme://$host$uri;
  }
}

medium

A. The URL is redirected to /example without trailing slash

B. The URL stays as /example/ with trailing slash

C. The server returns a 404 error

D. The URL is redirected to /example// with double slash

Solution

1. Step 1: Analyze the if condition

   The condition checks if the URL ends with a slash using regex ".+/$".

2. Step 2: Understand the redirect

   If true, it returns a 301 redirect to the same URL but without the trailing slash (because $uri excludes query string and trailing slash).

3. Final Answer:

   The URL is redirected to /example without trailing slash -> Option A

4. Quick Check:

   Trailing slash removed by redirect = The URL is redirected to /example without trailing slash [OK]

Hint: If URL ends with slash, return 301 redirects to no slash [OK]

Common Mistakes:

• Assuming URL stays unchanged
• Thinking server returns 404
• Expecting double slashes in redirect

4. Identify the error in this nginx config for adding trailing slashes:

location / {
  if ($request_uri !~ "/$") {
    return 301 $scheme://$host$uri/;
  }
}

medium

A. Using $request_uri instead of $uri causes double query strings

B. Missing semicolon after return statement

C. The regex should check for trailing slash presence, not absence

D. Using if inside location is not allowed

Solution

1. Step 1: Understand variables used

   $request_uri includes query string, $uri does not. Adding slash to $uri is safer.

2. Step 2: Identify problem with $request_uri

   Appending slash to $request_uri can cause double query strings or malformed URLs.

3. Final Answer:

   Using $request_uri instead of $uri causes double query strings -> Option A

4. Quick Check:

   Use $uri for clean URL redirects [OK]

Hint: Use $uri, not $request_uri, to avoid query duplication [OK]

Common Mistakes:

• Thinking if inside location is forbidden
• Ignoring query string issues
• Misreading regex logic

5. How would you configure nginx to always add a trailing slash to URLs except for requests to files (like .html or .jpg)?

hard

A. Use proxy_pass to add trailing slash

B. Always append slash to all URLs unconditionally

C. Use an if condition to check if URI lacks slash and does not end with a file extension, then return 301 with slash

D. Disable trailing slash normalization for all URLs

Solution

1. Step 1: Define condition for adding slash

   Check if URL does not end with slash and does not match file extensions like .html, .jpg.

2. Step 2: Use if and return 301 for redirect

   Use nginx if directive with regex to exclude files, then redirect to URL with trailing slash.

3. Final Answer:

   Use an if condition to check if URI lacks slash and does not end with a file extension, then return 301 with slash -> Option C

4. Quick Check:

   Conditional redirect excluding files = Use an if condition to check if URI lacks slash and does not end with a file extension, then return 301 with slash [OK]

Hint: Exclude files by regex, redirect others with slash [OK]

Common Mistakes:

• Appending slash to all URLs including files
• Using proxy_pass for redirects
• Disabling normalization entirely