dragonflymr
May 16, 2017Cirrostratus
Fallback Persistence Profile - how it works
Hi,
I don't know if this is bug or correct behavior - tested on 11.2.0
Setup:
-
VS with
- Default Persistence Profile: cookie insert
- Fallback Persistence Profile: source address
Result:
-
First request from client (without cookie):
- Set-Cookie header in response setting BIGipServer... cookie
- Persistence Record (PR) created - makes sense because there was no cookie in client request
-
Second request from client
- Cookie send in request
- PR timeout refreshed - could be OK as PR exists matching client IP but because Cookie is provided why it's used?
-
Third request - after PR was manually deleted
- Cookie send in request
- PR record created
Why PR is recreated when cookie exists? Which persistence is in fact used - cookie or source address?
Piotr