Nginx – How rewrite a URI in nginx

nginxrewrite

Please consider the following directory structure in my root:

/resources/css
/resources/js
/resources/templates
/resources/images

I want to serve static content from the above directories but
I also want to allow a rewrite like this to work:

rewrite ^/([a-z]+)(.*)$    /index.php?p1=$1&p2=$2;

For example myurl.com/register/... is rewritten to myurl.com/index.php?p1=register&p2=...

But that rule also rewrites /resources/, so how do I exclude /resources from the rewrite? Or do I need another rewrite? Nothing I've tried seems to work so obviously I'm not understanding something.

Best Answer

The config below is what I found that works, since the location statements are all the same precedence they are checked in order.

This helped me understand the precedence of location blocks:

location =  <path>  (longest match wins)
location ^~ <path>  (longest match wins)
location ~  <path>  (first defined match wins)
location    <path>  (longest match wins)

Here is the config:

// match all css/js/images in resource path

location ~ ^/resources {
        root   /mypath/myurl.com;
        try_files $uri =404;
        break;
}

// allow myurl.com/register etc:

location ~  ^/([a-z]+)/(.*)$ {
        root   /mypath/myurl.com;
        rewrite ^/([a-z]+)(.*)$    /index.php?p1=$1&p2=$2;
}

// everything else:

location ~ / {
    root   /mypath/myurl.com;
    index  index.php;
}

Comments welcome!

Correct way in new versions of nginx

Turn out my first answer to this question was correct at certain time, but it turned into another pitfall - to stay up to date please check Taxing rewrite pitfalls

I have been corrected by many SE users, so the credit goes to them, but more importantly, here is the correct code:

server {
       listen         80;
       server_name    my.domain.com;
       return         301 https://$server_name$request_uri;
}

server {
       listen         443 ssl;
       server_name    my.domain.com;
       # add Strict-Transport-Security to prevent man in the middle attacks
       add_header Strict-Transport-Security "max-age=31536000" always; 

       [....]
}

Nginx – What should the Nginx rewrite rules be for Rails with Passenger for page caching in a subdirectory

The answer was found here: https://stackoverflow.com/questions/1177979/nginx-rewrite-rules-with-passenger

The config ended up being:

# root
if (-f $document_root/cache/$uri/index.html) {
  rewrite (.*) /cache/$1/index.html break;
}

# pages like /about, cached with .html but accessed without
if (-f $document_root/cache/$uri.html) {
  rewrite (.*) /cache/$1.html break;
}

# pages like /api/v1/something.xml, cached as xml
if (-f $document_root/cache/$uri) {
  rewrite (.*) /cache/$1 break;
}

Best Answer

Related Solutions

NGINX Redirect – How to Rewrite All HTTP Requests to HTTPS While Maintaining Sub-Domain

Correct way in new versions of nginx

Nginx – What should the Nginx rewrite rules be for Rails with Passenger for page caching in a subdirectory

Related Topic