Comments on: Migrate from Apache to nginx (and keep rewrites intact)

By: Zach

Zach — Thu, 12 Jan 2012 05:43:46 +0000

Eddie: the try_files directive just gives nginx a fallback in case the request URI is invalid. Basic syntax would be something like this, based on your example:
try_files $uri $uri/ /index.php?url=$uri&$args;

By: Eddie

Eddie — Sun, 13 Feb 2011 16:22:16 +0000

@james

Thanks for the info!
I took a look at my config files and should be ok, runninga pretty recent version.

As for simplifying the wordpress script,i would love to hear more, perhaps am example.

By: James Nuvat

James Nuvat — Mon, 31 Jan 2011 17:41:44 +0000

Your example can be simplified significantly and it appears you are using old WordPress .htaccess rules. Use ‘try_files’ wherever possible because “if is evil” under nginx.

Also, be aware that bad configurations in nginx can and likely will introduce security vulnerabilities into your website. nginx is a proxy server first and a web server second, so it defaults to the assumption that files may not necessarily exist on the host it is running on and a simple regular expression can cause havoc. An example of this:

http://forum.nginx.org/read.php?2,88845

Took them way too long to come up with a reasonable solution to the problem. And, if you read through the conversation, people today are still getting bitten by the issue. As an added bonus, it doesn’t look like there will ever be a solution to the problem because it isn’t fixable and Igor isn’t interested in fixing it.

By: Running Pligg on Nginx – Rewrite rules | Edward A. Webb (.com)

Running Pligg on Nginx – Rewrite rules | Edward A. Webb (.com) — Fri, 19 Feb 2010 18:56:05 +0000

[...] I mentioned in my article “Migrate form Apache to Nginx and keep rewrite rules intact”, Nginx is an awesome and lightweight web [...]