PQ89746: WAS ADDS CACHE-CONTROL AND EXPIRES HEADERS AUTOMATICALLY WHEN A COOKIE IS ADDED. CUSTOMER DOES NOT WANT THESE ADDED. | |||||||||||||||||||||||||||||||||||||||||
![]() |
|||||||||||||||||||||||||||||||||||||||||
![]() APAR status Closed as program error. Error description Websphere sets the cache-control and expires headers automatically when a cookie is added. The customer does not want these headers set.Local fix Problem summary **************************************************************** * USERS AFFECTED: All users of WebSphere Application Server * * version 4.0.1 for z/OS and OS/390. * **************************************************************** * PROBLEM DESCRIPTION: Cache-Control and Expires Headers were * * being added by WebSphere Application * * Server when a cookie was being sent to * * the browser by the Application. * **************************************************************** * RECOMMENDATION: * **************************************************************** Whenever a cookie is returned by the servlet engine to the browser two headers namely "Expires" and "Cache-Control" are added to the HttpResponse. The "Expires" header is being set to a value of "Thu, 01 Dec 1994 16:00:00 GMT". With some old versions of browsers it was observed that the "Expires" header was causing the page not to be cached and on subsequent reloads of the page by clicking on the "Back Button" the request was being directed to the Application Server since the page had not been cached.Problem conclusion WebSphere Application Server code is modified to have the ability to suppress the generation of Cache-Control and Expires Headers as directed by the new was.conf property: appserver.java.extraparm= -Dcom.ibm.websphere.cookies.no.header=true (The above statement should be in one line) The new was.conf configuration property is processed by WebSphere Application Server. The property: appserver.java.extraparm=-Dcom.ibm.websphere.cookies.no.header may have the value "true" or "false". When com.ibm.websphere.cookies.no.header has the value "true" WebSphere Application Server will generate neither Cache-Control nor Expires Headers in the Http response. When com.ibm.websphere.cookies.no.header has the value "false" or is not specified, WebSphere Application Server will generate both Cache-Control and Expires Headers in the Http response. The default value is "false". The default behavior is to add the Cache-Control and Expires Headers. APAR PQ89746 is associated with SERVICE LEVEL W401613 of WebSphere Application Server version 4.0.1 for z/OS and OS/390.Temporary fix Comments
APAR is sysrouted FROM one or more of the following: PQ56395 APAR is sysrouted TO one or more of the following: Modules/Macros
|
Document Information |
Product categories: Software > Application Servers >
Distributed Application & Web Servers > WebSphere Application
Server for z/OS
Operating system(s):
Software version: 401
Software edition:
Reference #: PQ89746
IBM Group: Software Group
Modified date: Jul 2, 2004
(C) Copyright IBM Corporation 2000, 2006. All Rights Reserved.