[Zope-CMF] Zope cache problems

[Geoff Davis]

Dieter,

That would be perfect except for the fact that the Accelerated HTTP Cache
Manager doesn't work for pages from the file system, and the CSS files in
question all come from product skins and hence are file system objects.
It's really a bummer that the various cache managers each only operate in
certain domains.

Andy, this is a quick solution for your problem, though -- just customize
all the CSS in the Plone skins and then associate them with an Accelerated
HTTP Cache Manager.

Geoff Davis
http://www.geoffdavis.net


----- Original Message -----
From: "Dieter Maurer" <dieter@handshake.de>
To: "Geoff Davis" <geoff@geoffdavis.net>
Cc: "Andy Bramah" <andybramah@cantab.net>; "Plone Developers"
<plone-developers@lists.sourceforge.net>; "Zope CMF" <zope-cmf@zope.org>
Sent: Monday, August 19, 2002 4:01 PM
Subject: Re: [Zope-CMF] Zope cache problems


> Geoff Davis writes:
>  > ...
>  > What doesn't work:
>  >
>  > * When I hit the RELOAD button on my browser, the browser does a
conditional
>  > GET, which triggers validation on all objects.  Images correctly return
>  > 304's (no change), but style sheets and page templates return 200's
(they
>  > are completely re-sent).
> I think, this is not bad. You want to have a way to force
> reloads.
>
> My browser does even send an unconditional get when I press "reload".
>  > ...
>  > * The Plone CSS files are all generated by DTML scripts.
> CMF 1.3 comes with a cache manager.
> You can use it to control the generation of HTTP cache headers.
>
>
> Dieter
>