Rewrite flags (last, break, redirect, permanent) in Nginx - Mini Project: Build & Apply

Understanding Nginx Rewrite Flags: last, break, redirect, permanent

📖 Scenario: You are managing a website using Nginx web server. You want to control how URLs are rewritten and redirected to improve user experience and SEO.Different rewrite flags in Nginx change how the server handles URL changes. Learning these flags helps you control page redirects and URL rewriting effectively.

🎯 Goal: Build a simple Nginx configuration that uses the rewrite directive with the flags last, break, redirect, and permanent to see how each flag affects URL handling.

📋 What You'll Learn

Create a basic Nginx server block with a root location

Add rewrite rules using last, break, redirect, and permanent flags

Test each rewrite rule by simulating requests

Print or log the final rewritten URL or redirect status

💡 Why This Matters

🌍 Real World

Web servers often need to rewrite URLs to organize content better or redirect users to updated pages. Understanding rewrite flags helps manage these changes smoothly.

💼 Career

DevOps engineers and system administrators use Nginx rewrite rules to optimize web traffic, improve SEO, and maintain site structure without breaking links.

1

Create a basic Nginx server block

Write an Nginx server block listening on port 80 with a root directory set to /var/www/html. Inside the server block, create a location / block that serves files from the root directory.

Nginx

server {
    listen 80;
    root /var/www/html;

    location / {
        # Your code here
    }
}

Need a hint?

Use try_files $uri $uri/ =404; inside location / to serve files or return 404 if not found.

2

Add a rewrite rule with the last flag

Inside the location / block, add a rewrite rule that matches URLs starting with /oldpath and rewrites them to /newpath using the last flag.

Nginx

server {
    listen 80;
    root /var/www/html;

    location / {
        try_files $uri $uri/ =404;
        # Your code here
    }
}

Need a hint?

The last flag tells Nginx to restart the location search after rewriting the URL.

3

Add rewrite rules with break, redirect, and permanent flags

Add three more rewrite rules inside the location / block: one that rewrites /breakpath to /breaktarget using the break flag; one that redirects /redirectpath to /redirecttarget with a temporary redirect using the redirect flag; and one that redirects /permanentpath to /permanenttarget with a permanent redirect using the permanent flag.

Nginx

server {
    listen 80;
    root /var/www/html;

    location / {
        rewrite ^/oldpath(.*)$ /newpath$1 last;
        # Your code here
        try_files $uri $uri/ =404;
    }
}

Need a hint?

The break flag stops processing rewrite directives in the current location. The redirect flag sends a temporary redirect (302). The permanent flag sends a permanent redirect (301).

4

Print the final rewritten URL or redirect status

Add a return 200 directive inside the location / block that returns the rewritten URI using the variable $uri so you can see the final URL after rewrite rules are applied.

Nginx

server {
    listen 80;
    root /var/www/html;

    location / {
        rewrite ^/oldpath(.*)$ /newpath$1 last;
        rewrite ^/breakpath(.*)$ /breaktarget$1 break;
        rewrite ^/redirectpath(.*)$ /redirecttarget$1 redirect;
        rewrite ^/permanentpath(.*)$ /permanenttarget$1 permanent;
        try_files $uri $uri/ =404;
        # Your code here
    }
}

Need a hint?

The return 200 "$uri"; directive sends the current URI back in the response body so you can see the effect of rewrite rules.