Forum Discussion
Both iRule and Cookie persistence?
Detailed description part 3 of 3:
We tried setting sticky sessions using cookie persistence in hopes that it would help draining the sessions properly. However that seems to override the iRule so if a customer first goes to /a12345 (and gets a cookie) and then goes to /b12345 they would still end up at "server a" and get an error as the session does not exist there.
If we just use the iRule then the server is removed from the pool immediately and all users lose their work.
Anyone have any suggestion how this can be fixed or have any suggestion of another approach we can take to solve this problem?
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