Forum Discussion
peter_cuenco_73
Nimbostratus
NimbostratusPersistence within iRules
Hi,
I'm a newbie with iRules, but have a need for the following scenario -
VIP (my.company.com) is defined with cookie persistence. The VIP uses an iRule that basically reads -
...
I'm glad you asked. I've been doing some poking around on a similar question & have a few more details:
The way OneConnect works in v9 is somewhat different from v4, and in the earliest implementation (v9.0) we saw some unexpected behavior when combined w/cookie persistence, most of which seems to have been strightened out by the time 9.1 was released.
Cookie persistence works fine in 9.1 / 9.2, but apparently you MUST have OneConnect enabled to get cookie persistence to work properly /outside/ the context of iRules if connections will be kept alive by either LTM or the client.
If OneConnect is NOT enabled, the behaviour matches the v4 setting "web aggregate port, web parse first" which means aggregate only for same IP/port combination, and look at only the first request for persistence info. With that configuration, if subsequent requests from the same source submit different persistence cookies, they will be ignored, breaking cookie persistence.
CR62806 will be incorporated into a future release so the OneConnect profile is not required to use built-in cookie persistence with keepalive connections.
HTH
/deb
