Comments on: Finally using nginx's "try_files" directive

By: Ben

Ben — Thu, 06 May 2010 03:20:53 +0000

Thank you so much for this, it took me ages to find that I had to add &$args, something none of the other examples on other websites have shown, there are a few small things such as the theme preview in the WordPress admin that require this in order to work.

By: makuchaku

makuchaku — Mon, 19 Apr 2010 05:01:55 +0000

OMG! Can't tell you that how many people you have saved from going insane
Thanks for your post - just what's needed

By: Matthias Marschall

Matthias Marschall — Thu, 11 Mar 2010 10:38:11 +0000

We're using the permalink settings by wordpress. An article gets an URL like: http://www.agileweboperations.com/20-devops-guys. I cannot make it work:

The try_files approach works for the homepage and the backoffice (/wp-admin), but not for the pretty permalink urls.

The !-e approach works for home and permalinks but does not recognize /wp-admin as an existing directory and tries to redirect, too, which fails.

Anyone experienced similar issues? If it helps I can post my full nginx.conf of course...

By: jason wagner

jason wagner — Mon, 05 Oct 2009 19:13:07 +0000

Thank you!! The try_files line worked perfect for me.

location /blog/ {
   try_files $uri $uri/ /blog/index.php?q=$uri;
}

By: mike

mike — Fri, 17 Jul 2009 16:18:35 +0000

you are right. just a habit i suppose. might be interesting to look at the internals though, forcing the "q" parameter might cut down on some processing overhead (or vice-versa)

i need to look into trying to submit a patch to drupal to get them to handle the stuff with a / prefix being ignored. or ask someone. it must be a simple fix.

By: Otto

Otto — Fri, 17 Jul 2009 15:42:34 +0000

Or, if you prefer try_files:

try_files $uri $uri/ /wordpress/index.php;

By: Otto

Otto — Fri, 17 Jul 2009 15:40:35 +0000

Why are you adding the ?q= stuff? It's not necessary in the slightest.

if (!-e $request_filename) {
   rewrite ^ /index.php last;
}

Done. WordPress handles parsing the URL internally, all you have to do is force index.php to load. That's it.

By: mike

mike — Wed, 15 Jul 2009 16:05:48 +0000

I will issue a statement of caution - with Drupal, it will work, but depending on the plugins and modules you use it might break. This is something I need to draft up in a bug or something. I used to be able to have just:

try_files $uri $uri/ /index.php?q=$uri&$args;

However, $uri winds up inheriting a "/" at the beginning which breaks certain code. WordPress handles it just fine. Drupal can too, probably with a very simple line of code in how it parses URIs. For now this appears to be the safest bet:

if (!-e $request_filename) {
   rewrite ^/(.*)$ /index.php?q=$1 last;
}

Note: Drupal also hosts some stuff people shouldn't be accessing in the webroot (ugh) so marking those in a block as "internal" will keep people from accessing them. I still haven't validated that rule yet (I am just starting to support Drupal) but I always maintain my "do it in the simplest possible way" rule. A lot of the examples out there look like a mess and can probably be done a hell of a lot cleaner.

By: lury

lury — Wed, 15 Jul 2009 11:43:02 +0000

Thank you!

this fixed redirect loop problem with drupal, nginx and imagecache...
but i have no idea how.

By: mike

mike — Thu, 11 Jun 2009 23:23:02 +0000

That does not look right at all. That's setting the root to be the root of your filesystem?