Axel-Stéphane SMORGRAV wrote:
In that case my guess is that it is the application that generates erroneous
redirect URLs. Had tomcat generated the redirect URLs, theyr would have
contained the port number also, e.g. http://andy:8012/
Keep your configuration the way it is (ProxyPreserveHost Off
Brian Rectanus wrote:
It would help to post the tomcat-workers.conf, but I'll take a guess
and assume this is what it looks like:
LB1 andy:8012
LB2 andy:8022
LB3 andy:8032
LB3 andy:8042
ALL andy:8012|andy:8022|andy:8032|andy:8042
Yep, that's exactly what it looks like.
Does it make a
Boyle Owen wrote:
Let's focus on this bit:
however whenever there is an incoming POST
from a form in the web application, the response from the
Tomcat causes
a switch to HTTP, where I need it to remain HTTPS.
I'm not sure I completely understand.. When you say, "causes a switch to
Hello, I have a problem I've been grappling with for the past 3 days
without much luck so I thought I'd come to the experts. :-) I have
an Apache 2.0.x server, which acts as a load balancing gateway to
multiple Tomcat servlet containers behind it. This proxying/load
balancing is done usi