Dieter wrote: > 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 http://www.w3.org/Protocols/rfc2616/rfc2616-sec14.html#sec14.21 http://www.w3.org/Protocols/rfc2616/rfc2616-sec13.html#sec13.2 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 confusion? ] Bye, -- Bjorn _______________________________________________ Zope-Dev maillist - [EMAIL PROTECTED] http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
