Forum Discussion
jlarosa_44289
Nimbostratus
Aug 01, 2012Latest Exchange 2010 iApp (1.0.0.8) and Cookie Persistence
We are in the process of creating a new F5 11.2 load balanced solution for Exchange 2010 SP2 using a single VIP. After creating a new iApp based on the 1.0.0.8 Exchange 2010 template, I noticed the c...
mikeshimkus_111
Aug 01, 2012Historic F5 Account
That is correct, BIG-IP is inserting a cookie for persistence. In our testing, the OutlookSession cookie value can change mid-session, which could result in connections from the same client being sent to a different CAS. Also, using OutlookSession requires an entry in the BIG-IP persistence table while the BIG-IP cookie does not, making "cookie insert" more efficient.
For Outlook Anywhere, we persist on the value of the Authorization header, which should be unique if you're using Basic auth (which is recommended in the deployment guide).
The command "persist uie [HTTP::header "OutlookSession"]" was an error in the guide-OutlookSession is a cookie, not a header. You would want to use " "persist uie [HTTP::cookie "OutlookSession"]"" instead.
Recent Discussions
Related Content
DevCentral Quicklinks
* Getting Started on DevCentral
* Community Guidelines
* Community Terms of Use / EULA
* Community Ranking Explained
* Community Resources
* Contact the DevCentral Team
* Update MFA on account.f5.com
Discover DevCentral Connects