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: http://issues.apache.org/bugzilla/show_bug.cgi?id=19206
Alex -- Alexander Klimetschek http://www.mindquarry.com
