Hi @all!
The implementation of this method is the following:
<code>
if (moduleConfig.getControllerConfig().getNocache()) {
response.setHeader("Pragma", "No-cache");
response.setHeader("Cache-Control", "no-cache,no-store,max-age=0");
response.setDateHeader("Expires", 1);
}
</code>
The comment tells us that a call of the forward-method of RequestDispatcher will
override all header information and the SUN specification is supporting this
comment.
But why is it possible to configure cache control in the request processor if
every forward will override it?
We have explored this because the BEA Weblogic 8.1 does not implement correctly
the behaviour of the RequestDispatcher.forward - method. It doesn't reset the
headers, so if one module sets the no-cache attributes, every other module will
loose its cache, independent of its configuration. Be aware of this!
Bye,
Michael
http://www.struts-it.de
--
NEUSTA GmbH
Ostertorsteinweg 50
28203 Bremen
Tel.: +49 421 20696-22
Fax: +49 421 20696-99
Mobil: +49 171 4289299
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
