Nginx redirect without port

cloudflarenginxredirectvarnish

I have an issue with 301 redirects in Nginx. It always redirects to a URL with it's local port.

Situation is as follows: Site is running through Cloudflare, full https. CF sends http requests to the server where varnish accepts them. Varnish then passes the request on to nginx which handles the rest together with FPM.

Nginx is running on port 8080. I create a 301 redirect in Nginx like I usually do:

location = /url1 {
  return 301 /url2;
}

Nginx then redirects to the URL, but adds the original hostname & port it's running in (8080). So I set port_in_redirect to off in the server config. That works half. It'll redirect an http URL to https (without mentioning port 8080). It'll redirect an https URL to http though, loop.

How can I make sure that that doesn't happen? I wonder if it's possible to know the scheme that Cloudflare is servicing the request on as well.

Best Answer

Try to add absolute_redirect off to your location block

location = /url1 {
  absolute_redirect off;
  return 301 /url2;
}

Related Solutions

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.

Nginx – Redirect non-https traffic when using Varnish and nginx

You have two server blocks on port 81 with manager.domain.com configured as a host header - nginx has no way to know whether a request went through stunnel or not, so the first one wins and the redirect always occurs.

I'd recommend either having Varnish do the redirecting based on whether the request came from stunnel or not (check the request's client.ip - 127.0.0.1 means it's from stunnel), or have Varnish mark the requests from stunnel with a header so that nginx can decide how to handle them.

Best Answer

Related Solutions

NGINX Reverse Proxy – URL Rewrite

Nginx – Redirect non-https traffic when using Varnish and nginx

Related Topic