Welcome! Log In Create A New Profile

Advanced

Client specified server port

Joó Ádám
August 24, 2015 06:38PM
Hi,

The return directive allows the use of URLs relative to the server, in
which case the scheme, server name and port are automatically
prepended by Nginx.

The port is, however, the port on which the request was received,
which is not always the port to which the request was sent, i. e. the
one specified in the Host header field. For example, tunneling
nginx.org:80 through example.com:8000 a redirect will lead to
example.com:80.

Also, there is no variable exposing this value, so one must extract it
themselves to explicitly specify in the redirect URL:

set $is_port '';
set $port '';

if ($http_host ~ :(\d+)$) {
set $is_port ':';
set $port $1;
}

Maybe this is something that would worth considering as an
enhancement. Making return use the port in the Host header or to
preserve backwards compatibility, introducing a switch,
request_port_in_redirect, complementing server_name_in_redirect, off
by default, and at the same time exposing this in a $request_port
variable.

What do you think?


Ádám

_______________________________________________
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx
Subject Author Posted

Client specified server port

Joó Ádám August 24, 2015 06:38PM

Re: Client specified server port

ryd994 August 24, 2015 10:58PM

Re: Client specified server port

Francis Daly August 25, 2015 06:04PM



Sorry, only registered users may post in this forum.

Click here to login

Online Users

Guests: 92
Record Number of Users: 6 on February 13, 2018
Record Number of Guests: 421 on December 02, 2018
Powered by nginx      Powered by FreeBSD      PHP Powered      Powered by MariaDB      ipv6 ready