Forum Discussion

Travis_Brodeen_'s avatar
Travis_Brodeen_
Icon for Nimbostratus rankNimbostratus
Apr 29, 2005

Web Pool needs cookieless persistence

We have a Web Pool of 3 servers (IIS) that require a persistent SSL connection. Additionally, we would like to employ the SSL Termination features of the BIG-IP System, which offloads the SSL encryption/decryption from the web servers.

 

 

As an additional requirement, we cannot use the Cookie persistence to identify the end user, as our web application does not require cookies.

 

 

Aside from the Source IP persistence, can anyone confirm (or deny) that it will be possible to load balance traffic intelligently, while maintaining persistence through a custom iRule?

 

 

Any examples of this would be much appreciated!

 

 

Thank you,

 

 

Travis
application delivery
dev
devops
iRules
  • unRuleY_95363's avatar
    unRuleY_95363
    Historic F5 Account
    May 11, 2005
    You don't actually even need an iRule... You can use SSL session ID persistence which will (depending on the browser) persist all the same connections using the same SSL session to the same server. This can be enabled with the persist ssl setting on the virtual. You may also want to additionally use fallback persistence on the source IP to handle the transition some browsers go through while negotiating the SSL session. This is configured with the fallback persist srcaddr setting on the virtual.