session cookie persistence question

Thanks again for the input. I guess I didn't answer the question thoroughly last time. I'm using a standard oneconnect profile with an http compression profile with oneconnect enabled. The cookie persistence is a default insert with a session cookie. That seems to be the easiest way to persist on the 2 CAS servers i'm load balancing for OWA. I've tested this an it appears to work well. One thing to mention, there is a proxy on the edge terminating the user's https connection from the internet. The proxy is then making a call to the VIP Like I stated, I haven't really seen any issues. When I was testing the other night, I was trying to break it. IE having multiple browser sessions open, deleting temp files open new ones etc. I think it's ok from what I'm seeing. It's been live for 2 weeks now and our helpdesk hasn't seen any calls other than the standard "how to" type stuff.

 

 

Jayson