15 Sep
2003
15 Sep
'03
9:52 p.m.
On Sun, 2003-09-14 at 22:59, Bjorn Stabell wrote:
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
I reread the HTTP 1.1 spec and you are right. Section 13.4 allows any successful response to be cached unless prohibited by a cache-control directive, while it does not expect caching if there is neither a cache validator (ETag, Last-Modified) nor an expiration time. Dieter