Forum Discussion
NimbostratusBig-IP LTM - load balancing incoming request to 2 different 'paths' on Member Pool
NimbostratusThanks very much for your help! Really appreciated.
I added the web server certificate as a client/server SSL profile, this helped the F5 load balance as expected - however it still wasn't re-writing the URI (this was most likely a config issue on my end)
During out T/Shooting - we decided to go down the web server redirect route as this easy to implement.
HI chris_wood ,
Take Packet capture in both sides Client/server sides you will be able to see that Bigip rewrites your URI ,
Look at this from my enviroment after testing the iRule that I shred it with you :
where :
10.1.10.199 >>> Client address
10.1.10.100 >>> Virtual server
10.1.20.240 >>> F5 Bigip selfip address in server side/ ( intrtnal vlan)
10.1.20.11 >>> Server 1
Do you observe the rewriting of the uri , according to choose server 1 in loadbalancing.
Also this when Loadbalancing algorithm chose server 2 :
10.1.20.12 >>> server 2
So that take a packet capture that I sent in my last reply and the the change through F5 bigip first.
if the rewriting goes well , send it to the server owner and tell him that he needs some modification from his side as bigip did it's job.
Let me know if you need somthing
