Session timeout does not work for Outlook Web Access
Article ID: CTX233146
Updated On:
Description
Session timeout does not work for OWA.
Resolution
OWA keeps running monitoring scripts from the web. AppTimeout configuration defines the zombie behavior on idle tcp connections.
However, OWA continues to send requests that contains (UA=0/1) as a manner of polling the server. Server typically has the timeout implemented. Client removes session after that.
To circumvent this problem NetScaler offers a few solutions.
You can identify the patterns of the urls used for monitoring OWA, and bind them against a patset called ns_aaatm_norefresh_patterns
Example: bind patset ns_aaatm_norefresh_patterns “UA=0”
Once you do that, when traffic goes through NetScaler, for all above patterns, NetScaler will not extend the session time. This in turn results in session timing out early on NetScaler.
Other alternatives are using force timer (you can start/stop timer on the fly in policies
However, OWA continues to send requests that contains (UA=0/1) as a manner of polling the server. Server typically has the timeout implemented. Client removes session after that.
To circumvent this problem NetScaler offers a few solutions.
You can identify the patterns of the urls used for monitoring OWA, and bind them against a patset called ns_aaatm_norefresh_patterns
Example: bind patset ns_aaatm_norefresh_patterns “UA=0”
Once you do that, when traffic goes through NetScaler, for all above patterns, NetScaler will not extend the session time. This in turn results in session timing out early on NetScaler.
Other alternatives are using force timer (you can start/stop timer on the fly in policies
Was this article helpful?
Yes
No
Powered by
