Aaron, on tomcat instances change the redirectPort attributte on the http conectó to the loabbalancer's port 443
My guess is that your webapp has restriction rule requesting SSL con fidntial channel. Therefore the non-confidential to the 18080 port from the balancer are redirected to the 23270 port, but it should be 443. Antonio El 21/2/2017 19:46, "Aaron Gray" <aaronmg...@gmail.com> escribió: I have an application server from a vendor that comes bundled with an additional Apache Tomcat server. The webapp SelfService.war is vendor supplied too. Here's my problem (IP's replaced to protect the innocent): networks: DMZ=172.x.x.x INTERNAL=10.x.x.x server1 https listen = 172.1.1.1:23270 server2 https listen = 172.1.1.2:23270 F5 load balancer hostname = loadbalancer.domain.com:443 backend tomcat server = 10.1.1.1:18080 mod_proxy configuration: ProxyPass /SelfService http://10.1.1.1:18080/SelfService ProxyPassReverse /SelfService http://10.1.1.1:18080/SelfService When I access these DMZ webservers which mod_proxy back to Apache Tomcat as: https://172.1.1.1:23270/SelfService and https://172.1.1.2:23270/SelfService <https://172.1.1.1:23270/SelfService> They load properly. Perfectly, every time! When I access these DMZ webservers via the F5 load balancer (to which I dont have access to, but the network folks configure for me), it hangs. Eventually returns: https://loadbalancer.domain.com:23270/SelfService cant load. No idea why the URL is being re-written with the ":23270". I added static content to the server.xml on 10.1.1.1 (Tomcat) to test: <Context docBase="/path/to/tomcat/static" path="/static" /> Then put a simple index.html in there. Accessing via the Apache Web Servers works fine, but if you hit it with the Load Balancer it once again adds the https://loadbalancer.domain.com:23270/static Do you have any thoughts? Thanks so much, I have been working with this for weeks now with no success
