cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Miles Elam <>
Subject Re: Last-Modified and If-Modified-Since on pipelines
Date Sat, 03 May 2003 17:51:29 GMT
In my zeal to remove some preliminary ETag support so that you could 
have a clean patch, I dropped a very important routine from  Specifically, it just took 
System.currentTimeMillis().  The problem with this is that 999 times out 
of 1000, there will be some milliseconds added to seconds: the last 
modified value coming from the browser never has milliseconds.  
Therefore If-Modified-Since is invalid 999 times out of 1000 and 999 
times out of 1000, there will be no 304 response.

When I posted the last patch, I only checked in Mozilla to see that the 
last mod time didn't change.  It didn't.  But I never dropped to wget or 
telnet to check for 304...I just assumed.  Sorry about that Gianugo.

I've attached a fixed file to the bugzilla entry.  
(19206)  Just replace the caching/ in your tree and 

- Miles Elam

Gianugo Rabellino wrote:

> Patch applies cleanly now, thanks.
> Problem is I'm not getting the behaviour I expect. After applying your 
> patch, I fire up the Cocoon servlet and point my browser to 
> http://localhost:8888/samples/hello-world/hello.html, a caching 
> pipeline that should have no problem in caching the result and storing 
> the lastModified timestamp. On my first attempt I get:

View raw message