Server Fault is a question and answer site for system and network administrators. It's 100% free, no registration required.

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

Aim: To rewrite url's into a application compatible format

Progress: I have a rewrite from domain root that is working fine, however when I add /foo/ or /bar/ I just get a 404 as it tries to match that location within my config.

eg.. # Working fine # getting 404 - i assume it is failing to match location

I have the application url which I have added $request_uri to the end, however I want to be able to pass the /foo/ or /bar/ into the url to have it work correctly.

I have tried $request_body $request_uri$1 and varies combinations, however no luck just a 404.

How would I go about doing this? Which $variable do I need to pass into url?

An example of the url below. Not the exact one, but hopefully enough to get an idea.

location / {
    rewrite ^/$ pt/Wondering?virtual-webr00t=$request_uri` last;

location /pt/Wondering {

        proxy_set_header  X-Real-IP  $remote_addr;
        proxy_redirect off;
        proxy_buffering off;
        proxy_set_header        Host            $host;
        proxy_set_header        X-Real-IP       $remote_addr;
        proxy_set_header        X-Forwarded-For $proxy_add_x_forwarded_for;

        root    html;

share|improve this question
up vote 3 down vote accepted

Your problem is that you are using the below

rewrite ^/$   # Starts with / and ends with /

When you should be using

rewrite ^/ # start with / and accepts anything afterwards

The difference is the regex.

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.