[GeneralDiscussion] Re: zope/plone article

> Umm, the Last-Modified (conditional get) feature is ALREADY hardcoded.

Sorry, no, it isn't hardcoded at all. First of all it's an optional setting. Second, even if activated, Last-Modified uses, well, the "last modified" time, which by definition isn't a hard set value, like "max-age=86400" is. Someone might want to use another number for 86400, but "last time modified" isn't something that can be changed to another number.

> Adding Cache-Control is a bug fix i.e. making it work as it was thought Last-Modified should work.

No, the two can be combined, but do not have to be combined. Cache-Control is very much an admin defined setting.

> IMHO adding Accelerated HTTP Cache Manager support is a feature request and a totally separate issue.

It's something that already works, set one up, associate wiki pages with it, done.

I think the confusion arises because of your suggestion to use ``must-revalidate`` in the cache-control header. That is a good suggestion, but first, it would have to be optional (maybe combined with the Last-Modified setting) and second, no way am I going to agree to a hardcoded value for max-age just because we want to set ``must-revalidate``. Different sites may have vastly different notions of what is an acceptable value for max-age - if they want it set at all.

As I said before, the proper Zope way for the cache-control settings is to have these controls in an object where they can be set on a site-by-site basis. That's the way Plone does it (with their cache-fu tools), that's the way "Accelerated HTTP Cache Manager" is meant to be used.

--
forwarded from http://zwiki.org/GeneralDiscussion#[email protected]