Forum Discussion
May 03, 2011
Anyone run into a bug with "persist none" in 10.2?
I have a virtual server with:
rule myrule_443 {
when HTTP_REQUEST { set uri [string tolower [HTTP::uri]]
log local0.notice "Incoming Request uri: $uri"
if { [class match [HTTP::uri] starts_with myclass_443] } {
log local0.notice "Match"
persist none
pool not_my_default_pool
4 Replies
- Michael_Yates
Nimbostratus
That's an interesting problem.
The "persist none" is supposed to disable persistence when called, but it does not delete the Cookie so it should (in theory) not be used and just expire after the default cookie expiration, so how long do you see the cookie and are you being tied to the server specified in the cookie? - Colin_Walker_12Historic F5 AccountMichael makes a good point. The persist none command is intended to stop the persistence behavior, it's possible the cookie may still get inserted I suppose, I'd have to test this.
Can you verify that the persistence is still being enforced?
Colin - Figured out what was going here guys.. The iRrule and VS is functioning as intended.. There was a typo in the implimentors script and it assigned the wrong default pool to the VS.. Problem should be fixed once we get the fix into prod..
- Colin_Walker_12Historic F5 AccountWell there you go, that would do it. Nice find, and thanks for the update.
Colin
Recent Discussions
Related Content
DevCentral Quicklinks
* 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
Discover DevCentral Connects
