Hello! On Tue, Apr 05, 2016 at 02:12:21AM +0900, junpei yoshino wrote:
> which is better way ? > 1. > "real_ip_from Forwarded" replace remote_addr and remote_port. > And proxy_protocol also replace remote_addr and remote_port, too. While support for Forwarded is a good thing to have, it looks like a separate and big work, so I wouldn't recommend trying to do this now. > 2. > "real_port_from Forwarded" replace port only. > ip and port is independent. > Also proxy protocol must configure real_ip_from and real_port_from. This approach looks wrong. If we know client port it should be used. But see above about Forwarded. > 3. > At first, not care Forwarded header. > delete code related x-forwarded-port. > support only custom http header including port number. This option looks most appropriate for now. (Assuming this also includes "proxy_protocol also replace remote_addr and remote_port" as in 1.) -- Maxim Dounin http://nginx.org/ _______________________________________________ nginx-devel mailing list nginx-devel@nginx.org http://mailman.nginx.org/mailman/listinfo/nginx-devel
