Forum Discussion
question about Irule.
Cookie persistence is really just there to get the client to the same server throughout his session, and really has nothing to do with application session state. If for example you had no persistence, or persistence failed, and the LTM sent the user to the wrong server, the worst that should happen is that the user session blows up. I'm assuming that your application builds its own session with the client, presumably with a cookie. And so in order for you to experience a session jumping event, two clients would have to have the same application session cookie. Can you:
-
Replicate this event, and if so
-
Examine the application session cookies that are being used by each client - in other words, the application will send a session cookie to the client and the client will send this cookie back in each request. Is that cookie unique to a single client?
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