You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@cocoon.apache.org by Andreas Hartmann <an...@apache.org> on 2008/08/12 22:41:13 UTC
Problems with mod_cache + ResourceReader + status code 304
Hi Cocooners,
I'm trying to get mod_cache to work with Cocoon 2.1.6. Serving HTML
files works fine (after overriding the Serializer to set the
Content-Length header). There's a problem with Readers, though. All
requests are passed through to Cocoon and not cached by mod_cache. I
suspect that the problem is the 304 response which lacks the
Content-Length header (which is correct wrt the spec IIRC).
Do I have to modify the pipeline implementation to avoid sending a 304
response? Any hints how to solve this issue would be greatly appreciated!
TIA,
-- Andreas
--
Andreas Hartmann, CTO
BeCompany GmbH
http://www.becompany.ch
Tel.: +41 (0) 43 818 57 01
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@cocoon.apache.org
For additional commands, e-mail: users-help@cocoon.apache.org
[SOLVED] Problems with mod_cache + ResourceReader + status code 304
Posted by Andreas Hartmann <an...@apache.org>.
Andreas Hartmann schrieb:
> Hi Cocooners,
>
> I'm trying to get mod_cache to work with Cocoon 2.1.6. Serving HTML
> files works fine (after overriding the Serializer to set the
> Content-Length header). There's a problem with Readers, though. All
> requests are passed through to Cocoon and not cached by mod_cache. I
> suspect that the problem is the 304 response which lacks the
> Content-Length header (which is correct wrt the spec IIRC).
The problem has vanished after clearing the browser cache. Sorry for the
noise.
-- Andreas
--
Andreas Hartmann, CTO
BeCompany GmbH
http://www.becompany.ch
Tel.: +41 (0) 43 818 57 01
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@cocoon.apache.org
For additional commands, e-mail: users-help@cocoon.apache.org