Forum Discussion
question related to cookie
If your VSs are using different pools, then you would run into a problem, because the persistence cookie would hold the value for the specific node, so if your VSs have different pools with different nodes, the persistence cookie make force the request to the wrong node. Because of this, you could either use the default cookie persistence which will create a cookie based on the VS name and be more specific to that VS, or else you may look into something like source address persistence or universal persistence.
Help guide the future of your DevCentral Community!
What tools do you use to collaborate? (1min - anonymous)Recent Discussions
Related Content
* 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