Forum Discussion
SalishSeaSecurity
Altostratus
Jan 12, 2010Specifying node kills cookie persistence
I have a virtural server with a pool of four web servers. Load balancing is by least connection; oneconnect with a mask of 0.0.0.0 is enabled; persistence is by cookie insert (custom profile with non-...
hoolio
Cirrostratus
Jan 12, 2010If you don't get a conclusive response here, you might try opening a support case.
If all else fails, you could manually insert a persistence cookie in the response based on the manually selected server. The encoding algorithm (or the inverse, actually) is implemented in this Codeshare example
http://devcentral.f5.com/Wiki/default.aspx/iRules/Persistence_Cookie_Logger.html
And described in this AskF5 solution:
SOL6917: Overview of BIG-IP persistence cookie encoding
https://support.f5.com/kb/en-us/solutions/public/6000/900/sol6917.html
You'd probably want to do this once in RULE_INIT or per TCP connection for all the pool members to avoid performing the calculations on the response to every manually selected pool member request.
Aaron
Recent Discussions
Related Content
DevCentral Quicklinks
* Getting Started on DevCentral
* Community Guidelines
* Community Terms of Use / EULA
* Community Ranking Explained
* Community Resources
* Contact the DevCentral Team
* Update MFA on account.f5.com
Discover DevCentral Connects
