proxy_pass redirect for address without trailing slash disregards Host port

Nuno Gonçalves nunojpg at
Sat Aug 24 09:17:34 UTC 2019

On Sat, Aug 24, 2019 at 8:24 AM Jeffrey 'jf' Lim < at> wrote:
> The host is defined by the server, surely, and not by what the client tells the server it is? And you tell the server what host it is by the server_name directive (

That's not correct, the server is taking the Host domain part from the
client Host header. It's just not taking the port part.

This inconsistency is why I believe it's a bug.

For my exact case it was enough to set "absolute_redirect off;", since
only the absolute redirect is affected by this issue.


> -jf
> On Sat, 24 Aug 2019, 01:39 Nuno Gonçalves, <nunojpg at> wrote:
>> I am using proxy_pass and I'm facing a issue which I'm not sure it's a bug.
>> It is in regard to the behaviour specified by the documentation [1]:
>> If a location is defined by a prefix string that ends with the slash
>> character, and requests are processed by one of proxy_pass,
>> fastcgi_pass, uwsgi_pass, scgi_pass, memcached_pass, or grpc_pass,
>> then the special processing is performed. In response to a request
>> with URI equal to this string, but without the trailing slash, a
>> permanent redirect with the code 301 will be returned to the requested
>> URI with the slash appended. If this is not desired, an exact match of
>> the URI and location could be defined like this:
>> Consider that there is a proxy pass for location /abcd/ { proxy_pass
>> ... } for a server listening on port 80.
>> If I make a request for /abcd with Host header "",
>> then I receive a 301 for and not for the expected
>> In fact NGINX is considering the Host header domain part, but
>> disregarding the port part.
>> I believe this is a bug.
>> Thanks,
>> Nuno
>> [1]
>> _______________________________________________
>> nginx mailing list
>> nginx at
> _______________________________________________
> nginx mailing list
> nginx at

More information about the nginx mailing list