Keep Server Online
If you find the Apache Lounge, the downloads and overall help useful, please express your satisfaction with a donation.
or
A donation makes a contribution towards the costs, the time and effort that's going in this site and building.
Thank You! Steffen
Your donations will help to keep this site alive and well, and continuing building binaries. Apache Lounge is not sponsored.
| |
|
 Topic: Problems with mod_proxy and F5 load balancer |
|
| Author |
|
AMG1978
Joined: 07 Feb 2017
Posts: 7
Location: San Diego, CA
|
 Posted: Mon 13 Feb '17 22:55 Post subject: Problems with mod_proxy and F5 load balancer |
 |
|
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 as
https://172.1.1.1:23270/SelfService
and
https://172.1.1.1:23270/SelfService
They load properly. Perfectly.
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".
If you hit the LB with https://loadbalancer.domain.com/foo.html and that is in the main DocumentRoot, it works perfectly everytime. ONLY when I attempt to proxy with the F5 in front, do I run in to this strange issue.
Any thoughts? I appreciate your help.
:EDIT:
I added a second proxy of /foo and created static link in the internal 10.1.1.1:18080 with index.html
It proxies across beautifully with the load balancer. So perhaps this is some weird rewrite that is done via the application (vendor) in /SelfService ? What's strange is it doesnt do it if I hit the webserver directly. I opened a ticket with the vendor. |
|
| Back to top |
|
James Blond
Moderator
Joined: 19 Jan 2006
Posts: 7398
Location: EU, Germany, Next to Hamburg
|
| Posted: Sat 01 Apr '17 14:59 Post subject: |
|
|
| Were you able to solve the problem? |
|
| Back to top |
|
AMG1978
Joined: 07 Feb 2017
Posts: 7
Location: San Diego, CA
|
| Posted: Sat 01 Apr '17 16:23 Post subject: |
|
|
Yes. I updated to the latest release of Tomcat even though the vendor bundles it. They had a knowledge base article what to copy over to ensure the new one worked. They never told me this was their idea.
Whammo it worked perfectly!
So since they were like 25 releases back I asked them to find the reason in the release notes. I don't remember exactly now but it was like 7.0.62 area it was some bug in URI rewrites.
Annoying the whole time I had no idea.... but so glad I found the answer expeditiously on my own 
Vendor said try tweaking mod_proxy config to add a / at the end of the proxy but that didn't help. I got my solution, real happy. Thanks |
|
| Back to top |
|
|
|
|
|
|
