> Please read the HTTP 1.1 spec...
> Caching requires either an "ETag" or "Last-Modified" header.
> For good reasons...
That would explain why it never got "fixed", but that's not how I
understand the RFC: http://www.w3.org/Protocols/rfc2616/rfc2616.html
Indicates that "Expires" is enough to make content cacheable, and that
it should be considered "fresh" until its expire time unless clients or
servers use cache-control headers to force a revalidation.
Last-Modified and Etag are used to validate the content after it expires
using If-Modified-Since and If-None-Match respectively.
Is there a thread discussing this already somewhere?
[ Btw, Zope does return an empty Etag header; does that cause any
Zope-Dev maillist - [EMAIL PROTECTED]
** No cross posts or HTML encoding! **
(Related lists -