Forum Discussion
Turn persitence off for a pool
I have a virtual with a cookie persistence profile. There is an iRule that looks at the request URI and selects the correct pool for the request. This causes one or more persistence cookies to be added to the connection. One of the pools is for servers to serve up images and is thus stateless. However, the persistence setting on the virtual causes the requests to the image servers to also be persistent. How should I go about removing persistence for this pool but not the others?
I'm also thinking that oneConnect might also improve access to these images but, again this is applied at the virtual and might not be suitable for the other pools.
- hoolio
Cirrostratus
Hi Brian, - Hamish
Cirrocumulus
- Brian_Dantzig
Nimbostratus
OK. I looked under LB::persist rather than the persist statement. Thanks.
oneConnect looks useful but I've no experience with it and don't know if it's workable to turn it on and off based on the pool selected. I might be able to use it for the other servers as well but I don't know what situations might be problematic.
- hoolio
Cirrostratus
OneConnect should be a requirement when using L7 persistence like cookie insert. And it shouldn't hurt anything for non-session apps either. - nitass
Employee
this is sol which Aaron mentioned about oneconnect and L7 persistence.
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