Hi Mel, symptoms of the session cookie persistence bug would include clients being forced to reauthenticate in the middle of a session, after the (incorrectly configured) cookie expired: http://support.f5.com/kb/en-us/solutions/public/11000/600/sol11679.html
The uglobal.js/owa.ev/Accept-Encoding header changes both address the same issue, which is caused by the Exchange server not FINing the connection on requests for files larger than a certain size when using dynamic compression. This would show up as a hanging browser immediately after login. You would not be able to click on anything in the OWA interface, and if you looked at a packet capture, you would see that requests for those files would never complete.
thanks
Mike
