Nginx – Removing trailing slashes from certain URL’s in nginx

nginxrewrite

I recently moved my blog from using WordPress over to using Jekyll (I like the idea of static files for my blog). I'm using Nginx (was using it with PHP-FPM before) and have things setup to handle stuff. I've encountered one problem I do not know how to fix.

The URL structure I'm using is

/atthekeyboard/YYYY/MM/DD/title-of-post

I have about 5 years worth of blog posts that have been indexed by Google and they are

/attheykeyboard/YYYY/MM/DD/title-of-post/

I want to rewrite all the older calls with the trailing slash to use the non-trailing slash URL until Google indexes all the new stuff.

Here is the nginx config stuff I have already:

    location /atthekeyboard {
            index index.html;
            try_files $uri.html $uri/ /notfound.html;
    }

I'm using try_files because the posts are actually saved as title-of-post.html and I didn't want the .html part.

Thanks in advance for your advice and solutions!

Best Answer

Something like this should remove the trailing slash and then let Nginx reparse the location blocks.

location ~ ^(/atthekeyboard/.+)/$ {
    set $noslash $1;
    rewrite ^ $noslash permanent;
}

Related Solutions

How to remove trailing slashes from a URL when using Apache’s default directory index file

You could always use mod_rewrite to redirect the directory name without the trailing slash to dirname/index.html. You could use RedirectConds to make sure that redirection doesn't get done if the URL ends with a trailing slash or with .html, and that it only applies specifically to blog post URLs.

Let me whip up an example, this'll take a moment.

# Trailing slashes and .html suffix
RewriteCond !/$
RewriteCond !\.html$

# Check if it's actually a dir and if index.html exists
RewriteCond %{REQUEST_URI} -d
RewriteCond %{REQUEST_URI}/index.html -f

# Rewrite anything that gets through (Probably insecure, but you get the idea)
RewriteRule ^(.*)$ $1/index.html

Edit: Can also be combined with Matt's solution of adding the redirect error code to the RewriteRule. It should probably also be made the last RedirectRule. Refer to the mod_rewrite documentation for more.

nginx try_files – How Does try_files Work in nginx?

try_files tries the literal path you specify in relation to the defined root directive and sets the internal file pointer. If you use for instance try_files /app/cache/ $uri @fallback; with index index.php index.html; then it will test the paths in this order:

$document_root/app/cache/index.php
$document_root/app/cache/index.html
$document_root$uri

before finally internally redirecting to the @fallback named location. You can also use a file or a status code (=404) as your last parameter but if using a file it must exist.

You should note that try_files itself will not issue an internal redirect for anything but the last parameter. Meaning you cannot do the following: try_files $uri /cache.php @fallback; as that will cause nginx to set the internal file pointer to $document_root/cache.php and serve it, but since no internal redirect takes place the locations aren't re-evaluated and as such it will be served as plain text. (The reason it works with PHP files as the index is that the index directive will issue an internal redirect)

Best Answer

Related Solutions

How to remove trailing slashes from a URL when using Apache’s default directory index file

nginx try_files – How Does try_files Work in nginx?

Related Topic