Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

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

I currently have nginx setup to serve content through Varnish. Nginx listens on port 8000 and varnish connects users' requests from 80 to 8000.

The problem is, on some occasions, particularly when trying to hit a directory, like, nginx is redirecting the request to

How can I prevent this?

share|improve this question
up vote 6 down vote accepted

I found the answer to this question by more carefully reading the HttpCoreModule docs.

port_in_redirect off;

This retains the port used by the client during redirects. Closely related is server_name_in_redirect which uses the first hostname for redirects. As I didn't want to redirect to,

share|improve this answer

The code behind NGINX probably uses the FASTCGI variable SERVER_PORT to determine where to direct the user. SERVER_PORT will contain the port nginx listens on, so that would be 8000 in your case.

You can try something like this for testing purpose:

location ~ \.php$ {
        fastcgi_param  SERVER_PORT 80;

adapted to your configuration. That's a dirty hack but can help you diagnose the problem.

share|improve this answer

For those who have

  • Varnish listens port 80
  • backend server (in my case nginx) listens port 8080

The fastcgi_param SERVER_PORT should be same as the frontend.

So, I set

fastcgi_param  SERVER_PORT 80;

to redirect to appropriate URL from nginx.

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.