Nginx – How to match string in URL using Nginx

nginxreverse-proxyrewrite

I have sett up reverse proxy with Nginx reverse proxy is just working fine as expected.
I have another scenario where i need to redirect URL based on matching string using proxy_pass.

ie : http://xx.xx.xx.xx:81/crawlers/587dbbf8e4b0b5cea2c4a49e/execute?url=https%3A%2F%2Fwww.massimodutti.com%2Fes%2Fhombre%2Faccesorios%2Fbolsas-c1748214p7722308.html%3Fkeyword%3DBANDOLERA%2520PEQUE%25C3%2591A%2520PIEL%2520BURTON%26colorId%3D700&token=5892cf1cf056fa9ac307a39c&

This is the rest call i want if URL contains massimodutti.de so it should be route to german servers using proxy_pass

currently i am blank and searching for solution any help will be highly appreciated…

Best Answer

You should use the nginx map feature to map query arguments into proxy_pass destinations. It works like this:

In the nginx configuration http level, you add a map like this:

map $arg_url $proxyserver {
    default default.server;
    "~\.de" german.server;
}

where you replace default.server with the domain name for default server and german.server with the domain name for your german server.

Then, you use proxy_pass http://$proxyserver; in your server block for the reverse proxy destination definition.

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 Reverse Proxy – URL Rewrite

Any redirect to localhost doesn't make sense from a remote system (e.g. client's Web browser). So the rewrite flags permanent (301) or redirect (302) are not usable in your case.

Please try following setup using a transparent rewrite rule:

location  /foo {
  rewrite /foo/(.*) /$1  break;
  proxy_pass         http://localhost:3200;
  proxy_redirect     off;
  proxy_set_header   Host $host;
}

Use curl -i to test your rewrites. A very subtle change to the rule can cause nginx to perform a redirect.

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 Reverse Proxy – URL Rewrite

Related Topic