cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Alexander Klimetschek <>
Subject Re: Broken caching of servlet: source in some cases
Date Fri, 20 Apr 2007 13:29:27 GMT
Alexander Klimetschek schrieb:
> Well, there are multiple fixes. The best one IMHO is to fix a bug in 
> HttpEnvironment.isResponseModified() [1]. It should *not* set the 
> Last-Modified value if it is invalid == -1 (which is the case if the 
> servlet source cannot determine the last modified value).

> AFAIK setting a "-1" last modified header is not according the HTTP 
> spec, one should not include the header in that case. But why am I the 
> first one to spot that problem? It's a central part of cocoon's caching 
> algorithm.

Just an additional note: the original patch and related discussion can be 
found here:


Alexander Klimetschek

View raw message