Forum Discussion

AMiles_377865's avatar
AMiles_377865
Icon for Cirrocumulus rankCirrocumulus

Hello Adam,

 

Have you instead looked into HTTP::redirect?

 

This would change your flow so that the client sends a separate HTTP request to vs1 and vs2, making a separate connection to your other virtual servers. It might simplify your configuration a little more. That way you could do source_addr persistence, etc.

 

Best of luck,

 

Austin

 

adam88's avatar
adam88
Icon for Cirrus rankCirrus
Apr 12, 2019

Unfortunately HTTP:redirect is not an option because in order to switch traffic to the other virtual server, I will either have to:

  1. Redirect the user to a different sub-domain that resolves to the IP address of the other virtual server (eg. https://vs2.example.com)
  2. Redirect the user to the same sub-domain but add a custom port at the back of the hostname (https://www.example.com:5000/abc)

Both these options are unacceptable as the requirement is that the whole thing is transparent to the users and that the user's browser address bar only shows either https://www.example.com/abc or https://www.example.com/def.