It's probably not necessary to enforced the no cache here. I will
review the codes and see if they should be changed. Any comment from
the group?
David
On Thursday, Dec 26, 2002, at 15:57 Asia/Shanghai, Mathieu Peltier
wrote:
-----------------------------------------------------------------------
----------------------------------
Subject: Any reason to overwrite Response Header in XMLCContext ?
Date: Tue, 24 Dec 2002 12:31:58 -0500
From: "Zhihai Li" <Zhihai.Li@xxxxxxxxxx>
To: <xmlc@xxxxxxxxxxx>
In XMLCContext (v 1.4)
private void outputHeaders(HttpServletResponse response,
int docLength,
String mimeEncoding,
String mimeType,
boolean compressed)
...
// Disable caching of page unless otherwise specified.
if (response.containsHeader("Cache-Control")) {
response.setHeader("Cache-Control", "no-cache");
}
if (response.containsHeader("Expires")) {
response.setHeader("Expires", "0");
}
...
Is there any reason to just check if you set Expires header or not ,
set it
to 0. but not use the original value.
We have the server site caching problem for the Resin 2.x version .
since
Resin expecting a default value on this header,
if this value was overwrited , Resin will caculate wrong expiration
date from
server site, so the page get requested
will never expired from the sever side.
Is this the Resin bug or the XMLC bug, if it is a bug ?
Thanks .
-----------------------------------------------------------------------
----------------------------------
--
Mathieu Peltier
INRIA Rhône-Alpes - ObjectWeb Consortium
http://www.inrialpes.fr/ - http://www.objectweb.org/
Computer programmers do it byte by byte.
_______________________________________________
XMLC mailing list
XMLC@xxxxxxxxxxx
http://www.enhydra.org/mailman/listinfo.cgi/xmlc
| 