By Serafeim

2013-07-02 09:55:17 8 Comments

I am using the following configuration for nginx 1.4.1:

server {
    listen       8000;

    location /test/register {
        proxy_set_header X-Forwarded-Host $host;
        proxy_set_header X-Forwarded-Server $host;
        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;

What I want to do is when the users vist they should be proxied to the apache which runs on port 80.

When I visit I get correct results (index.php). When I visit I get correct results (404 from apache). When I visit I get correct results (404 from nginx). When I visit I get correct results (404 from apache).

The problem is when I visit I get a 301 response and I am redirected to http://localhost/test/register/ (notice the trailing slash and of course the 'localhost')!!!

I haven't done any other configurations to nginx to put trailing slashes or something similar. Do you know what is the problem ? I want to work correctly by proxying to apache (or if not possible at least to issue a 404 error and not a redirect to the localhost of the user).

Update 1: I tried from a different computer than the one with which I had the bad behavior yesterday.. Well, it worked: I just got a 301 response that pointed me to the correct! How is it possible to work from one computer but not from the other (I'm using the same browser-Chrome in both computers)? I will try again tomorrow to test from a third one to see the behavior.

Thank you !


@Chuan Ma 2013-07-04 03:47:11

My guess is that your upstream server (either apache or your script) triggered a redirect to the absolute url http://localhost/test/register/. Because you use in your proxy_pass directive, nginx doesn't find a match of the domain name and returns the Location header as is.

I think the right solution is to NOT use absolute redirect if the redirect is to an internal url. This is always a good practice.

However, without changing upstream server, there are two quick solutions.

you can use

proxy_pass http://localhost;

This will tell nginx the domain name of upstream is localhost. Then nginx will know to replace http://localhost by when it finds that part in the Location header from upstream.

Another one is to add a proxy_redirect line to force nginx to rewrite any location header with http://localhost/ in it.

 proxy_redirect http://localhost/ /;

I prefer to the first solution because it's simpler. There is no DNS lookup overhead of using proxy_pass http://localhost; because nginx does the lookup in advance when it starts the web server.


@vreen 2013-07-03 20:47:25

Did you already try playing with server_name_in_redirect?

However, I found you question via google because I run the same issue with the trailing slash. Nginx forces a 301 to the same URL with an trailing slash.

@Serafeim 2013-07-03 22:53:51

No I did not try playing with that... I will tomorrow - however take a look at the update pls

@vreen 2013-07-04 12:59:37

Just to avoid any browser caching side effects, I would rather recommend testing these redirects with curl from a shell: "curl -IL"

@Serafeim 2013-07-04 14:45:32

Yes, very nice comment... Curl FTW !

Related Questions

Sponsored Content

12 Answered Questions

[SOLVED] Node.js + Nginx - What now?

  • 2011-02-15 20:49:02
  • Van Coding
  • 338828 View
  • 969 Score
  • 12 Answer
  • Tags:   node.js nginx concept

19 Answered Questions

2 Answered Questions

Keycloak Redirect url with nginx is going to http rather than https

  • 2018-04-03 12:02:15
  • Atulya Nair
  • 1543 View
  • 4 Score
  • 2 Answer
  • Tags:   nginx jboss

1 Answered Questions

[SOLVED] Nginx reverse proxy to Apache with DirectorySlash directive

  • 2019-01-24 18:48:13
  • richbai90
  • 50 View
  • 1 Score
  • 1 Answer
  • Tags:   apache nginx

2 Answered Questions

Reverse Proxy with NGINX and Docker

2 Answered Questions

[SOLVED] Why is my Nginx reverse proxy doing a 301 redirect instead of proxying?

2 Answered Questions

2 Answered Questions

How to point many paths to proxy server in nginx

Sponsored Content