Forum Discussion
Verifying Cookie Persistence
The simple answer here is when you specify a secondary persistence it always runs both but only uses the second if the first cannot be found. Its easy to test, try accessing your application until you get sent to the second pool member. Now write the value of BIGipServer cookie down. Clear all cookies and wait for source persistence records to expire. Now with round robin as your load balancing access your application and you should get a cookie for the first server and a persistence record for same. Now clear cookies and try is again. You will go back to the first server because of the persistence record and the cookie will reappear on the client side as the F5 will create one. Now clear cookies again and craft a request using the cookie you wrote down. Now you will go to the second server.
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