Home / server / Questions / 532571
Accepted
hendry
Asked: 2013-08-22 02:15:51 +0800 CST

Apache to Nginx rewrite rules

  • 772

I have Apache rules for a Web application that look like so:

RewriteEngine On
RewriteRule ^unsubscribe/([-A-z0-9]+)/?(.*)$ /list/unsubscribe.php?id=$1&why=$2 [L,QSA]
RewriteRule ^unsub/([-A-z0-9]+)/?(.*)$ /list/subscribe.php?id=$1&why=$2 [L,QSA]

I've tried:

rewrite ^unsubscribe/([-A-z0-9]+)/?(.*)$ /list/unsubscribe.php?id=$1&why=$2;

Which didn't seem to match and results in a 404.

    location /unsubscribe {
        rewrite ^/unsubscribe/([-A-z0-9]+)/?(.*)$ /list/unsubscribe.php?id=$1&why=$2 break;
    }

Results in serving the file, but without PHP processed http://sg.hackandtell.org/unsubscribe/foo/bar

Perhaps can someone recommend some debug strategies?

nginx

2 Answers

  1. Best Answer

    I don't have a debug strategy, so I am not 100% sure what nginx is doing. Though I rewrote the rewrite rules like so:

    rewrite ^/unsubscribe/([a-zA-Z0-9]*)$ /list/unsubscribe.php?id=$1;
rewrite ^/unsub/([a-zA-Z0-9]*)$ /list/subscribe.php?id=$1;
rewrite ^/unsubscribe/([a-zA-Z0-9]*)/(.*)$ /list/unsubscribe.php?id=$1&why=$2;
rewrite ^/unsub/([a-zA-Z0-9]*)/(.*)$ /list/subscribe.php?id=$1&why=$2;

    And it works. :)

    • 0

  2. The nginx Wiki states:

    last - completes processing of current rewrite directives and restarts the process (including rewriting) with a search for a match on the URI from all available locations.

    break - completes processing of current rewrite directives and non-rewrite processing continues within the current location block only.

    So when using break, it will use the server {...}-wide root directive (I assume you have one) and serve the file statically.

    You should rather try last in your rewrite rule, because then the PHP-processing route will match in a second turn and direct the request to PHP.

    • 0