cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From giacomo <>
Subject Re: bug - c2 is caching too aggressively!
Date Sun, 15 Jul 2001 16:29:24 GMT
On Sat, 14 Jul 2001, Donald Ball wrote:

> On Sat, 14 Jul 2001, giacomo wrote:
> > The 304 code should only be set if there was a is-modified-since header
> > presented from the client (browser).
> >
> > Everything else is nonsens.
> that's what i thought too, and the code seems to back us up, but my
> _experience_ has been different. i was hoping to see if anyone else shared
> the same _experience_. this isn't _nonsense_, i'm trying to track down a
> bug.

To be honest, the code base has grown very quickly the last few month.
I thought that the 304 was only produced by the ResourceReader so far
but it seems that other parts of the code will produce 304 as well.
Actually I don't know which part is also producing 304 but a find/grep
should uncover those parts.


To unsubscribe, e-mail:
For additional commands, email:

View raw message