Forum Discussion

Art_Sholty_6751's avatar
Art_Sholty_6751
Icon for Nimbostratus rankNimbostratus
Jan 27, 2015

Cookies and Persistence methods

I am trying to solve an issue with cookie based persistence. I am using a simple iRule to look for the presence of a value within a cookie. If the value exists, the user is assigned to a specific pool. User's without this value go to the default pool. The issue I seem to be having is that not every incoming request, that compose the page, specifically those requesting static assets, contain the cookie. When I check for cookies, I can see two persist records; one for the desired pool and one for the default. Would I be better off using a hash method and inserting a cookie, which I could then check to determine the proper pool, or is there a simpler method?

 

application delivery
devops
iRules
LTM

1 Reply

Sort By
  • OTS02's avatar
    OTS02
    Icon for Cirrus rankCirrus
    Jan 27, 2015

    Interesting scenario. Rather than persist on the cookie, you could direct to the pool, and then persist on the source IP. However, if there are multiple user/clients behind a proxy, then all behind the proxy will persist to the "cookie" pool. I think you will end up having to insert a cookie as well. And I think you will have to create a UIE persistence profile. Hoolio helped me with this - the thread name is "universal persistence using jsessionid".