https://github.com/Pylons/waitress/pull/249 1.2.1 (2019-01-25) Bugfixes When given an IPv6 address in X-Forwarded-For or Forwarded for= waitress was placing the IP address in REMOTE_ADDR with brackets: [2001:db8::0] waitress-serve \ --listen "*:$PORT" \ --trusted-proxy '*' \ --trusted-proxy-headers 'x-forwarded-for x-forwarded-proto x- forwarded-port' \ --log-untrusted-proxy-headers \ --clear-untrusted-proxy-headers environment using X-Forwarded-Proto, X-Forwarded-For, X-Forwarded-Host, and X-Forwarded-Port: proxy_set_header X-Forwarded-Proto $scheme; proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for; proxy_set_header

https://github.com/Pylons/waitress/pull/249 1.2.1 (2019-01-25) Bugfixes When given an IPv6 address in X-Forwarded-For or Forwarded for= waitress was placing the IP address in REMOTE_ADDR with brackets: [2001:db8::0] waitress-serve \ --listen "*:$PORT" \ --trusted-proxy '*' \ --trusted-proxy-headers 'x-forwarded-for x-forwarded-proto x- forwarded-port' \ --log-untrusted-proxy-headers \ --clear-untrusted-proxy-headers environment using X-Forwarded-Proto, X-Forwarded-For, X-Forwarded-Host, and X-Forwarded-Port: proxy_set_header X-Forwarded-Proto $scheme; proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for; proxy_set_header

https://github.com/Pylons/waitress/pull/249 1.2.1 (2019-01-25) Bugfixes When given an IPv6 address in X-Forwarded-For or Forwarded for= waitress was placing the IP address in REMOTE_ADDR with brackets: [2001:db8::0] waitress-serve \ --listen "*:$PORT" \ --trusted-proxy '*' \ --trusted-proxy-headers 'x-forwarded-for x-forwarded-proto x- forwarded-port' \ --log-untrusted-proxy-headers \ --clear-untrusted-proxy-headers environment using X-Forwarded-Proto, X-Forwarded-For, X-Forwarded-Host, and X-Forwarded-Port: proxy_set_header X-Forwarded-Proto $scheme; proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for; proxy_set_header

https://github.com/Pylons/waitress/pull/249 1.2.1 (2019-01-25) Bugfixes When given an IPv6 address in X-Forwarded-For or Forwarded for= waitress was placing the IP address in REMOTE_ADDR with brackets: [2001:db8::0] environment using X-Forwarded-Proto, X-Forwarded-For, X-Forwarded-Host, and X-Forwarded-Port: proxy_set_header X-Forwarded-Proto $scheme; proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for; proxy_set_header X-Forwarded-Port $server_port; when using Apache, mod_proxy automatically forwards the following headers: X-Forwarded-For X-Forwarded-Host X-Forwarded-Server You will also want to add to Apache: RequestHeader set

when using Nginx: proxy_set_header X-Forwarded-Proto $scheme; It’s permitted to set an X-Forwarded-For header too; the PrefixMiddleware uses this to adjust other environment variables (you’ll have its docs to find out which ones, I don’t know what they are). For the X-Forwarded-For header: proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for; Note that you can wrap your application

configure Tomcat’s RemoteIpValve if you enable it. This allows you to transparently use the standard x-forwarded-for and x- forwarded-proto headers that most front-end proxy servers add. The valve is switched on and if you only set one the other will be set automatically): server.tomcat.remote_ip_header=x-forwarded-for server.tomcat.protocol_header=x-forwarded-protocol If your proxy uses different headers you The standard behavior is determined by the presence or absence of certain request headers (x-forwarded-for and x-forwarded-proto), whose names are conventional, so it should work with most front end proxies

configure Tomcat’s RemoteIpValve if you enable it. This allows you to transparently use the standard x-forwarded-for and x- forwarded-proto headers that most front-end proxy servers add. The valve is switched on and if you only set one the other will be set automatically): server.tomcat.remote_ip_header=x-forwarded-for server.tomcat.protocol_header=x-forwarded-proto If your proxy uses different headers you can The standard behavior is determined by the presence or absence of certain request headers (x-forwarded-for and x-forwarded-proto), whose names are conventional, so it should work with most front end proxies

valve by adding some entries to application.properties, e.g. server.tomcat.remote_ip_header=x-forwarded-for server.tomcat.protocol_header=x-forwarded-proto Alternatively, you can add the RemoteIpValve The standard behavior is determined by the presence or absence of certain request headers (x-forwarded-for and x-forwarded-proto), whose names are conventional, so it should work with most front end proxies valve by adding some entries to application.properties, e.g. server.tomcat.remote_ip_header=x-forwarded-for server.tomcat.protocol_header=x-forwarded-proto (The presence of either of those properties

configure Tomcat’s RemoteIpValve if you enable it. This allows you to transparently use the standard x-forwarded-for and x- forwarded-proto headers that most front-end proxy servers add. The valve is switched on and if you only set one the other will be set automatically): server.tomcat.remote_ip_header=x-forwarded-for server.tomcat.protocol_header=x-forwarded-proto If your proxy uses different headers you can The standard behavior is determined by the presence or absence of certain request headers (x-forwarded-for and x-forwarded-proto), whose names are conventional, so it should work with most front end proxies

configure Tomcat’s RemoteIpValve if you enable it. This allows you to transparently use the standard x-forwarded-for and x- forwarded-proto headers that most front-end proxy servers add. The valve is switched on and if you only set one the other will be set automatically): server.tomcat.remote_ip_header=x-forwarded-for server.tomcat.protocol_header=x-forwarded-proto If your proxy uses different headers you can The standard behavior is determined by the presence or absence of certain request headers (x-forwarded-for and x-forwarded-proto), whose names are conventional, so it should work with most front end proxies