Forum Discussion
Cookie persistence and source address fallback
- Apr 20, 2015
You are correct when putting Cookie and Source Persist together. If there is a persist record it will go to that server and cluster all the clients that share the same IP to the same server.
When using different browsers you will have the same cookie name of "BIGipServer_keycloak", but the cookie values themselves should be different. Is this not the case?
Edited. Cookie values can be the same.
My values are not different, they are the same. And i think, they should be different. (i am using different firefox user profiles).
- Feb 26, 2025
The cookie values
should be differentbetween Firefox user profiles as each user profile maintains its own set of cookies.
Edited. Cookie values can be the same.- kbksFeb 26, 2025
Altostratus
OK so what is wrong here? How can i check where is the problem and fix the issue?
- Feb 26, 2025
Apologies, I take back what I said. It's perfectly normal to have the same cookie value between different browsers. If you were to decrypt and / or decode the cookie value, you would see that it just reveals the back-end pool member's IP address (which is how the BIG-IP knows which pool member to send the request to).
So, there's nothing wrong. Nothing to fix.
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