Webpage expiration errors when using session persistence on WebSphere Application Server
WebSphere Application Server (WAS) adds expired header to the response when using session persistence and the WebSphere Extreme Scale client.
Webpage expiration errors.
The WebSphere Extreme Scale Client adds two cookies for each user: IBMID and IBMSessionHandle_<grid> in the response. When the WXS client is running on WebSphere Application Server (WAS) the presence of a Set-Cookie header in the HTTP response message triggers WAS to add cache related headers. One of these HTTP headers is the expire header set to very old date. The old date in the expire header will cause the webpages to automatically expire.
The WAS HTTP transport channel custom property CookiesConfigureNoCache controls adding cache headers when the Set-Cookie header is present in the HTTP response.
Diagnosing the problem
Check the HTTP response for an expire header with a very old date.
Resolving the problem
Use the CookiesConfigureNoCache property to specify whether the presence of a Set-Cookie header in an HTTP response message triggers the addition of several cache related headers. If this property is set to true, an Expires header with a very old date, and a Cache-Control header that explicitly tells the client not to cache the Set-Cookie header are automatically added. These headers are not automatically added if this property is set to false.
This property is functionality equivalent to the com.ibm.websphere.cookies.no.header property that was available in previous versions of WebSphere Application Server.
This is a WebSphere application property and not WebSphere eXtreme Scale properties. More information about this property can be found at:
More support for:
WebSphere eXtreme Scale
Software version: 8.5, 22.214.171.124
Operating system(s): AIX, IBM i, Linux, Solaris, Windows, z/OS
Reference #: 1614057
Modified date: 30 September 2015