environment settings. This allows you to transparently use the standard x- forwarded-for and x-forwarded-proto headers that most front-end proxy servers add. You can switch on the valve by adding some entries properties, e.g. server.tomcat.remote_ip_header=x-forwarded-for server.tomcat.protocol_header=x-forwarded-proto Alternatively, you can add the RemoteIpValve yourself by adding a TomcatEmbeddedServletContainerFactory 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. You can switch on the

environment settings. This allows you to transparently use the standard x-forwarded-for and x-forwarded- proto headers that most front-end proxy servers add. You can switch on the valve by adding some entries properties, e.g. server.tomcat.remote_ip_header=x-forwarded-for server.tomcat.protocol_header=x-forwarded-proto Alternatively, you can add the RemoteIpValve yourself by adding a TomcatEmbeddedServletContainerFactory 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. You can switch on the

environment settings. This allows you to transparently use the standard x- forwarded-for and x-forwarded-proto headers that most front-end proxy servers add. You can switch on the valve by adding some entries properties, e.g. server.tomcat.remote_ip_header=x-forwarded-for server.tomcat.protocol_header=x-forwarded-proto Alternatively, you can add the RemoteIpValve yourself by adding a TomcatEmbeddedServletContainerFactory 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. You can switch on the

environment settings. This allows you to transparently use the standard x-forwarded-for and x-forwarded- proto headers that most front-end proxy servers add. You can switch on the valve by adding some entries properties, e.g. server.tomcat.remote_ip_header=x-forwarded-for server.tomcat.protocol_header=x-forwarded-proto Alternatively, you can add the RemoteIpValve yourself by adding a TomcatEmbeddedServletContainerFactory 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. You can switch on the

environment settings. This allows you to transparently use the standard x-forwarded-for and x-forwarded- proto headers that most front-end proxy servers add. You can switch on the valve by adding some entries properties, e.g. server.tomcat.remote_ip_header=x-forwarded-for server.tomcat.protocol_header=x-forwarded-proto Alternatively, you can add the RemoteIpValve yourself by adding a TomcatEmbeddedServletContainerFactory 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. You can switch on the

environment settings. This allows you to transparently use the standard x- forwarded-for and x-forwarded-proto headers that most front-end proxy servers add. You can switch on the valve by adding some entries properties, e.g. server.tomcat.remote_ip_header=x-forwarded-for server.tomcat.protocol_header=x-forwarded-proto Alternatively, you can add the RemoteIpValve yourself by adding a TomcatEmbeddedServletContainerFactory 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. You can switch on the

environment settings. This allows you to transparently use the standard x- forwarded-for and x-forwarded-proto headers that most front-end proxy servers add. You can switch on the valve by adding some entries properties, e.g. server.tomcat.remote_ip_header=x-forwarded-for server.tomcat.protocol_header=x-forwarded-proto Alternatively, you can add the RemoteIpValve yourself by adding a TomcatEmbeddedServletContainerFactory 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. You can switch on the

environment settings. This allows you to transparently use the standard x-forwarded-for and x-forwarded- proto headers that most front-end proxy servers add. You can switch on the valve by adding some entries properties, e.g. server.tomcat.remote_ip_header=x-forwarded-for server.tomcat.protocol_header=x-forwarded-proto Alternatively, you can add the RemoteIpValve yourself by adding a TomcatEmbeddedServletContainerFactory 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. You can switch on the

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 by setting one or both of automatically): server.tomcat.remote_ip_header=x-forwarded-for server.tomcat.protocol_header=x-forwarded-proto If your proxy uses different headers you can customize the valve’s configuration by adding some entries 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. You can switch on the

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 by setting one or both of automatically): server.tomcat.remote_ip_header=x-forwarded-for server.tomcat.protocol_header=x-forwarded-proto If your proxy uses different headers you can customize the valve’s configuration by adding some entries 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. You can switch on the