using nginx try_files and autoindex together

Question

I have the following server configuration:

server {
    listen 80;
    server_name _;

    root /var/www/;

    location /calendars/ {
        autoindex on;
        try_files $uri.ics $uri =404;
    }
}

If would expect to get the autoindex page on visiting http://example.com/calendars/, however I get an 404 File not found error instead.

I want the server do something like this pseudo-code:

if($uri is directory) {
    if(one of index pages exists in directory) {
        show index page;
    } else {
        show autoindex page;
    }
} else {
    if($uri.ics exists) {
        show $uri.ics;
    } else if($uri exists) {
        show $uri;
    } else {
        show 404 page;
    }
}

score 7 · Accepted Answer · edited Apr 11 '17 at 16:19

7

You also need a check for the directory in try_files if you want the directory index loaded or autogenerated.

try_files $uri.ics $uri $uri/ =404;

Per the documentation for the try_files directive:

It is possible to check directory’s existence by specifying a slash at the end of a name, e.g. $uri/

In other words, $uri means "try a file at the given path", whereas $uri/ means "try a directory at the given path", and the latter is what causes auto-indexing of that directory to kick in.

edited Apr 11 '17 at 16:19

mindplay.dk

103
3

answered Mar 27 '13 at 02:43

Michael Hampton

237,123
42
477
940

This works, but I don't understand why. If I visit `/calendar/` wouldn't `$uri == "/calendar/"` and `$uri/ == "/calendar//"`? – Tyilo Mar 27 '13 at 11:40
1

Did you click the link? It explains: It doesn't _actually_ append a `/`, but instead loads the directory index if available. – Michael Hampton Mar 27 '13 at 11:49
I hadn't noticed the link as I'm colorblind. – Tyilo Mar 27 '13 at 11:54
Blame the developers. They're hard to see for the rest of us, too. :) – Michael Hampton Mar 27 '13 at 11:56

using nginx try_files and autoindex together

1 Answers1