Forum Discussion
Irules and persistence
We have a vip with an irule attached to it. The vip is configured with Match across virt servers persistence. In the Irule we proxy out various sub directories. For Example: https://www.myurl.com/security Goes off to an F5 pool on port 7499 (the client stays at https://www.myurl.com/security) Base upon this article: https://devcentral.f5.com/articles/persisting-across-virtual-servers It suggests that I need to manage the persistence in the Irule so that a client on https://www.myurl.com/security always gets the same /security server for the life of there session. Is that correct?
- Alex
1 Reply
- Kevin_Stewart
Employee
It suggests that I need to manage the persistence in the Irule so that a client on https://www.myurl.com/security always gets the same /security server for the life of there session.
I certainly think it'd be preferred, but I don't think it's expressly required. Are you matching across virtuals because the client is actually touching multiple virtual servers? Your description doesn't really allude to that, and if it's simply URI-based load balancing to different pools, the built-in cookie persistence profile should be able to handle that for a single VIP.
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