Why Rewrite flags (last, break, redirect, permanent) in Nginx? - Purpose & Use Cases

The Big Idea

Discover how a few simple flags can save your website from broken links and lost visitors!

The Scenario

Imagine you manage a website and need to change many URLs manually in your server settings every time you update your site structure.

You have to edit each URL one by one in multiple places, which is confusing and takes a lot of time.

The Problem

Manually updating URLs is slow and easy to mess up.

You might forget to update some links or create loops that break your site.

This causes bad user experience and lost visitors.

The Solution

Rewrite flags in nginx let you control how URL changes happen automatically.

They help you decide when to stop rewriting, when to redirect users, and how to do it cleanly.

This makes your site faster and easier to manage.

Before vs After

✗ Before

if ($request_uri = "/old-page") {
  return 301 /new-page;
}
# Repeat for every URL

✓ After

rewrite ^/old-page$ /new-page permanent;
# One line handles the redirect cleanly

What It Enables

You can easily manage URL changes and redirects without breaking your site or confusing users.

Real Life Example

When you redesign your website and move pages, rewrite flags help send visitors from old URLs to new ones smoothly.

Key Takeaways

Manual URL changes are slow and error-prone.

Rewrite flags automate and control URL handling.

This improves site reliability and user experience.

Practice

1. What does the last flag do in an nginx rewrite directive?

easy

A. Stops processing the current location and restarts the rewrite phase with the new URI

B. Sends a temporary redirect (HTTP 302) to the client

C. Stops processing the rewrite directives and continues with the current location

D. Sends a permanent redirect (HTTP 301) to the client

Solution

1. Step 1: Understand the last flag behavior

   The last flag tells nginx to stop processing current rewrite directives and restart the rewrite phase with the new URI.

2. Step 2: Compare with other flags

   Unlike break which stops rewriting internally, last restarts processing, and unlike redirect or permanent which send redirects, it does not send a client redirect.

3. Final Answer:

   Stops processing the current location and restarts the rewrite phase with the new URI -> Option A

4. Quick Check:

   last = restart rewrite phase [OK]

Hint: Remember: last restarts rewrite, break stops internally [OK]

Common Mistakes:

• Confusing last with break flag
• Thinking last sends a redirect
• Mixing last with permanent redirect

2. Which of the following is the correct syntax to perform a permanent redirect in nginx using the rewrite directive?

easy

A. rewrite ^/old$ /new break;

B. rewrite ^/old$ /new last;

C. rewrite ^/old$ /new permanent;

D. rewrite ^/old$ /new redirect;

Solution

1. Step 1: Identify the flag for permanent redirect

   The permanent flag sends an HTTP 301 status code indicating a permanent redirect.

2. Step 2: Check syntax correctness

   The syntax rewrite ^/old$ /new permanent; correctly applies the permanent redirect flag.

3. Final Answer:

   rewrite ^/old$ /new permanent; -> Option C

4. Quick Check:

   Permanent redirect uses permanent flag [OK]

Hint: Permanent redirect uses 'permanent' flag at end [OK]

Common Mistakes:

• Using 'last' or 'break' instead of 'permanent' for redirects
• Omitting the semicolon at the end
• Confusing 'redirect' with 'permanent'

3. Given the nginx configuration snippet:

location /test {
  rewrite ^/test/(.*)$ /new/$1 redirect;
}

What will happen when a client requests /test/page?

medium

A. The client will receive a 301 permanent redirect to /new/page

B. The rewrite will restart processing with the new URI /new/page

C. The request will be internally rewritten to /new/page without redirect

D. The client will receive a 302 temporary redirect to /new/page

Solution

1. Step 1: Understand the redirect flag

   The redirect flag sends an HTTP 302 temporary redirect to the client.

2. Step 2: Analyze the rewrite rule

   The rewrite matches /test/page and rewrites it to /new/page with a temporary redirect.

3. Final Answer:

   The client will receive a 302 temporary redirect to /new/page -> Option D

4. Quick Check:

   redirect = 302 temporary redirect [OK]

Hint: redirect flag means 302 temporary redirect [OK]

Common Mistakes:

• Confusing redirect with permanent
• Thinking redirect rewrites internally
• Assuming last or break flags here

4. You have this nginx rewrite rule:

rewrite ^/oldpath/(.*)$ /newpath/$1 last

But it causes a 500 Internal Server Error. What is the likely problem?

medium

A. Missing semicolon at the end of the rewrite directive

B. Using 'last' flag instead of 'break' causes infinite loop

C. The regex pattern is invalid

D. Rewrite directive must be inside a location block

Solution

1. Step 1: Check syntax of rewrite directive

   Every nginx directive must end with a semicolon. The given rewrite lacks a semicolon.

2. Step 2: Understand error cause

   Missing semicolon causes nginx to fail parsing config, leading to 500 error.

3. Final Answer:

   Missing semicolon at the end of the rewrite directive -> Option A

4. Quick Check:

   Missing semicolon = syntax error = 500 error [OK]

Hint: Always end rewrite directives with semicolon [OK]

Common Mistakes:

• Assuming last flag causes infinite loop
• Ignoring missing semicolon syntax errors
• Thinking regex pattern is wrong without checking

5. You want to rewrite URLs starting with /app to /app/index.html internally without redirecting the client, and stop further rewrite processing. Which rewrite directive and flag should you use?

hard

A. rewrite ^/app$ /app/index.html last;

B. rewrite ^/app$ /app/index.html break;

C. rewrite ^/app$ /app/index.html redirect;

D. rewrite ^/app$ /app/index.html permanent;

Solution

1. Step 1: Identify internal rewrite without client redirect

   The break flag stops rewrite processing and serves the rewritten URI internally without redirecting the client.

2. Step 2: Match requirement to flag

   Using break with the rewrite stops further rewrites and serves /app/index.html internally.

3. Final Answer:

   rewrite ^/app$ /app/index.html break; -> Option B

4. Quick Check:

   break = internal rewrite stop [OK]

Hint: Use break to rewrite internally and stop further rewrites [OK]

Common Mistakes:

• Using last which restarts rewrite phase
• Using redirect or permanent which send client redirects
• Not stopping rewrite processing causing unexpected behavior