ASP.NET persistence vs BIG-IP cookie

Hi, Thanks for explanation. I've got the point with app session cookie being possible more granular (can change more often than BIG-IP). Then it seems that using app cookie will potentially allow for better LB, when application finishes given session for given user then there is no more need to send another user session to the same server - but it most probably will be the case with BIG-IP cookie. Seems that stuff related to app session can really get complicated with multiple apps running on the same FQDN :-( But I am still curious if duplicate cookies from my example are something usual or not really - notice that two .ASPXANONYMOUS has same value as well as two ASP.NET_SessionId. My Universal persitnece is in the end generating two Persistence Records as result - both are identical - that seems to be overhead and can use resources. What is as well interesting why those cookies has so long expiration - around two months. What factors do you advice to analyse to decide which kind of persistence will be best for given application? Piotr

The 2 cookie values being the same may be different users - see here - https://stackoverflow.com/questions/2448720/different-users-get-the-same-cookie-value-in-aspxanonymous The cookie timeouts are up to the application owners to set or modify. As far as what type of persistence I would use on a given application I typically use this line of thoughts: Does the application require new layer 4 connections to go to the same host if so: * Does the application have an LTM application layer profile to track it (like FTP, SIP, etc.) if so, use that and no persistence should be required * Is the Application HTTP based (and if encrypted can I decrypt it?) if so I typically use cookie insert, with source ip address as a backup * Is there some other type of object or offset in a request I can use to indicate a session inside the application request to make a decision, like part of a SQL update statement, FQDN, E.164, etc.

Thanks, will have to dig in a bit. I doubt doubled cookies are because or other user. I tested it with cache and cookies cleared, just one connection to the main page of the site. I checked link you posted but it's about ASPXANONYMOUS cookie. I am more concerned about repeating of ASP.NET_SessionId (the one I based mu universal persistence). I am not very good in web developing are so I am not sure if I should bother customer to verify why this cookie repeating occurs. Piotr