Add slash to the end of every url (need rewrite rule for nginx)

Question

I try to get an / to every urls end:

example.com/art

should

example.com/art/

I use nginx as webserver.

I need the rewrite rule for this..

For better understanding check this:

http://3much.schnickschnack.info/art/projekte

If u press on a small thumbnail under the big picture it reloads and shows this url:

http://3much.schnickschnack.info/art/projekte/#0

If i now have a slash on all urls (on the end) it would work without a reload of the site.

Right now i have this settings in nginx-http.conf:

server {
  listen *:80;
  server_name 3much.schnickschnack.info;
  access_log /data/plone/deamon/var/log/main-plone-access.log;
  rewrite ^/(.*)$ /VirtualHostBase/http/3much.schnickschnack.info:80/2much/VirtualHostRoot/$1 last;
  location / {
    proxy_pass http://cache;
  }
}

How do I configure nginx to add a slash? (I think i should a rewrite rule?)

I need it for a js gallery. If there is no "/" it reloads the site... — Gomez, Mar 14 '09 at 12:39
So the question is "How do I configure nginx to add a slash?" Or is it "How do I configure nginx to work without a slash?" — S.Lott, Mar 14 '09 at 17:15

score 141 · Answer 1 · edited Jan 13 '12 at 14:06

141

More likely I think you would want something like this:

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

The Regular Expression translates to: "rewrite all URIs without any '.' in them that don't end with a '/' to the URI + '/'" Or simply: "If the URI doesn't have a period and does not end with a slash, add a slash to the end"

The reason for only rewriting URI's without dots in them makes it so any file with a file extension doesn't get rewritten. For example your images, css, javascript, etc and prevent possible redirect loops if using some php framework that does its own rewrites also

Another common rewrite to accompany this would be:

rewrite ^([^.]*)$ /index.php;

This very simply rewrites all URI's that don't have periods in them to your index.php (or whatever file you would execute your controller from).

edited Jan 13 '12 at 14:06

anthonysomerset

546
4
14

answered Oct 12 '10 at 08:11

Bob Monteverde

1,419
1
9
2

3

This is the only post on the interwebs that doesn't add a trailing slash to EVERYTHING. thanks for posting. – ansiart Oct 20 '11 at 15:19
this one works much more reliably particularly with php frameworks that do there own pretty link rewriting – anthonysomerset Jan 13 '12 at 11:45
I have static html files so this: **http://domain.com/about** gets the file **http://domain.com/about.html** but still shows the URL without ".html". I am looking to add a slash after I hit the file but get a 404 now if I add a slash. So I want to remove the trailing slash (if exists) and with or without trailing slash gets "-html" file but shows "/" after. This does not work: ``rewrite ^/([a-zA-Z0-9]+)$ /$1.html; rewrite ^([^.]*[^/])$ $1/ permanent;`` Also for click on "about" in a menu severa times I get this **http://domain.com/about/about/about/** etc.. – Asle Jan 09 '17 at 12:50
What about query strings? – Benubird Nov 15 '17 at 09:59
@EtienneMartin It looks like it will rewrite `domain.com/page?thing=abc` into `domain.com/page?thing=abc/`. Or does nginx detect and handle query strings separately? – Benubird Jan 04 '19 at 09:50
@Benubird Yes I thought the same when I saw it but it tested it and it looks like query strings are handled separately. – Etienne Martin Jan 04 '19 at 15:45
I could be doing something wrong here, but unfortunately this seems to break down when working with nested directories. I don't have nginx so I'm just testing it against https://regex101.com/ so removing the beginning of line condition to operate on the full URL `http://example.com/foo/bar`, the pattern `[^.]*[^/]$` matches `com/foo/bar`. `\/\w+[^.][^/]$` on the other hand, matches `/bar` but not `/bar.html` or `/bar/` – hyperwiser Nov 13 '19 at 18:01
Unfortunately, this doesn't seem to work if the URL contains a port: http://localhost:8080/something turns into http://localhost/something :T – Efrain May 27 '21 at 17:12

score 32 · Answer 2 · answered May 19 '13 at 23:01

32

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

to avoid querystrings of a rest url getting a / tagged on.

e.g.

/myrest/do?d=12345

answered May 19 '13 at 23:01

Marc

6,773
10
44
68

2

how could you make the result ``` /myrest/do/?d=12345 ``` – Patrick Lee Scott Apr 08 '16 at 03:03
@PatrickLeeScott Adding '?' to regex to exclude would be sufficient I think – Satish Patro May 29 '21 at 06:53
@PatrickLeeScott I'd added an answer that case – Mechanic Jan 11 '22 at 19:39

score 7 · Answer 3 · answered Sep 25 '10 at 01:26

7

For nginx:

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

answered Sep 25 '10 at 01:26

bryan

2,223
1
22
19

5

This will add a slash to EVERYTHING - so you'll end up with index.php -> index.php/, and page?a=b -> page?a=b/ where what the OP surely wants is page?a=b -> page/?a=b – Benubird Nov 15 '17 at 10:00

Andrew Dinmore · Answer 4 · 2016-12-12T18:12:22.850

Odd that this is the first result in Google, but doesn't have a satisfactory answer. There are two good ways to do this I know of. The first is to straight-up check if the request will hit a file and only apply a rewrite condition if not. E.g.

server {
   # ...
   if (!-f $request_filename) {
     rewrite [^/]$ $uri/ permanent;
   }
   location / {
      # CMS logic, e.g. try_files $uri $uri /index.php$request_uri;
   }
   # ...
}

The second, which many prefer as they'd rather avoid any use of if that isn't 100% necessary, is to use try_files to send the request to a named location block when it won't hit a file. E.g.

server {
   # ...
   location / {
      try_files $uri $uri/ @cms;
   }
   location @cms {
      rewrite [^/]$ $uri/ permanent;
      # CMS logic, e.g. rewrite ^ /index.php$request_uri;
   }
   # ...
}

Kai · Answer 5 · 2016-02-01T08:44:54.787

3

it's too late but I want to share my solution, I've met issue with trailing slash and nginx.

#case : 
# 1. abc.com/xyz  => abc.com/xyz/
# 2. abc.com/xyz/ => abc.com/xyz/
# 3. abc.com/xyz?123&how=towork => abc.com/xyz/?123&how=towork
# 4. abc.com/xyz/?123&ho=towork => abc.com/xyz/?123&how=towork

and this is my solution

server { 
    ....
    # check if request isn't static file
    if ($request_filename !~* .(gif|html|jpe?g|png|json|ico|js|css|flv|swf|pdf|xml)$ ) {
       rewrite (^[^?]+[^/?])([^/]*)$ $1/$2 permanent;
    }
    ....
    location / {
    ....
    }
}

edited Feb 01 '16 at 08:44

answered Feb 01 '16 at 07:30

Kai

3,104
2
19
30

I really like your solution. It helped me :). It can be also imporved with a more gneric regex for file matching: `if ($request_filename !~* .[a-zA-Z0-9]+$ )` This should match any file. – Andreas Hauschild May 24 '21 at 17:30

score 2 · Answer 6 · answered Jul 24 '15 at 08:59

server {
    # ... omissis ...

    # put this before your locations
    rewrite ^(/.*[^/])$ $1/ permanent;

    # ... omissis ...
}

If you want some kind of requests (say other than GET ones) to be prevented from doing this (usually it's about POST requests, as rewrite turns any request method into GET, which may break some of your site's dynamic functionality), add an if clause:

server {
    # ... omissis ...

    # put this before your locations
    if ($request_method = "GET" ) {
        rewrite ^(/.*[^/])$ $1/ permanent;
    }

    # ... omissis ...
}

You can also put the rewrite in a location block (if too), to make it more specific.

score 1 · Answer 7 · answered Mar 12 '14 at 01:27

using the rewrites from anthonysomerset in a Wordpress, I experimented problems accesing to /wp-admin dashboard due to reirection loop. But i solve this problem using the above conditional:

if ($request_uri !~ "^/wp-admin")
{
rewrite ^([^.]*[^/])$ $1/ permanent;
rewrite ^([^.]*)$ /index.php;
}

score 0 · Answer 8 · answered Mar 16 '18 at 06:29

If nginx behind proxy with https, this snippet do correct redirect for $scheme

map $http_x_forwarded_proto $upstream_scheme {
    "https" "https";
    default "http";
}

server {
    ...
    location / {
        rewrite ^([^.\?]*[^/])$ $upstream_scheme://$http_host$1/ permanent;
    }
    ...
}

And on the upstream proxy pass the X-Forwarded-Proto header like:

location / {
    proxy_set_header X-Forwarded-Proto $scheme;
    ...
}

score 0 · Answer 9 · answered Jan 11 '22 at 19:17

This rule solves query string case too:

location ~ ^/([^.]*[^/])$ {
  if ($query_string) {
    return 301 $scheme://$host/$1/?$query_string;
  }
  return 301 $scheme://$host/$1/;
}

The regex has taken from @marc's answer: rewrite ^([^.\?]*[^/])$ $1/ permanent;

The extra slash ^/ in regex is added to improve readability

score 0 · Answer 10 · answered Aug 01 '23 at 17:50

0

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

just add this

answered Aug 01 '23 at 17:50

artcozlove

1

score -4 · Answer 11 · answered Mar 14 '09 at 12:48

-4

Try this: ^(.*)$ http://domain.com/$1/ [L,R=301]

This redirects (Status code 301) everything ($1) without a "/" to "$1/"

answered Mar 14 '09 at 12:48

Mork0075

5,895
4
25
24

Gomez: You should absolutely 301 (redirect) the non-slashed URL to the slashed one, or search-engines and such will see example.com/blah and example.com/blah/ as two completely separate pages – dbr Mar 14 '09 at 14:00
I just tested this. ^(.*)$ redirects everything regardless. I had to use ^(.*)[^/] instead, so it only redirects if there's no ending slash. – Chris Aug 12 '09 at 19:06
12

This answer appears to provide syntax for Apache, but the original question is for nginx. – bryan Sep 25 '10 at 01:20

Add slash to the end of every url (need rewrite rule for nginx)

11 Answers11

Linked