Cyrille Le Clerc
[email protected], http://blog.xebia.fr/
Cyrille Le Clerc
[email protected], http://blog.xebia.fr/
Backlink Service - High PageRank Backlinks to have you flying up through the SERP
Cyrille Le Clerc
[email protected], http://blog.xebia.fr/
Backlink Service - High PageRank Backlinks to have you flying up through the SERP
Andrew Swanson wrote:
I am using the RemoteIpValve to correctly set request.isSecure and request.scheme but I am using the "ProxyPreserveHost" Apache httpd directive so that request.serverHost and request.serverPort are correctly set in Tomcat. Is there anyway to prevent RemoteIpValve from populating the request.serverPort when it detects the presence of the $protocolHeader http header?
Cyrille Le Clerc
[email protected], http://blog.xebia.fr/
Cyrille Le Clerc wrote:Hello Andrew,
You are right, RemoteIpValve (and RemoteIpFilter) currently override the serverPort when you specify a protocol header (e.g. x-forwarded-proto). Would you like to add a boolean configuration option override-http-server-port-with-protocol-information to disable this behavior for your use case ?
Thanks for your interest in RemoteIpValve,
Cyrille
Andrew Swanson wrote:
I am using the RemoteIpValve to correctly set request.isSecure and request.scheme but I am using the "ProxyPreserveHost" Apache httpd directive so that request.serverHost and request.serverPort are correctly set in Tomcat. Is there anyway to prevent RemoteIpValve from populating the request.serverPort when it detects the presence of the $protocolHeader http header?
YSPanwar
Space pants. Tiny ad:
Smokeless wood heat with a rocket mass heater
https://woodheat.net
|