For more information regarding the security incident at F5, the actions we are taking to address it, and our ongoing efforts to protect our customers, click here.

Forum Discussion

Christer_377235's avatar
Christer_377235
Icon for Nimbostratus rankNimbostratus
Nov 19, 2018

Both iRule and Cookie persistence?

Is it possible to have a rule where you redirect to pool members depending on url (always has priority) but you also have some kind of persistence table so you can drain connections so users are not ...
application delivery
BIG-IP
Christer_377235's avatar
Christer_377235
Icon for Nimbostratus rankNimbostratus
Nov 19, 2018

Detailed description part 3 of 3:

 

We tried setting sticky sessions using cookie persistence in hopes that it would help draining the sessions properly. However that seems to override the iRule so if a customer first goes to /a12345 (and gets a cookie) and then goes to /b12345 they would still end up at "server a" and get an error as the session does not exist there.

 

If we just use the iRule then the server is removed from the pool immediately and all users lose their work.

 

Anyone have any suggestion how this can be fixed or have any suggestion of another approach we can take to solve this problem?