- From: Jeffrey Mogul <mogul@pa.dec.com>
- Date: Fri, 31 May 96 14:13:16 MDT
- To: Koen Holtman <koen@win.tue.nl>
- Cc: http-wg%cuckoo.hpl.hp.com@hplb.hpl.hp.com, mogul@pa.dec.com
Based on all this, I propose that the sentence
HTTP/1.1 caches MUST send an Age header in every response.
in 16.4 is changed into
HTTP/1.1 caches MUST send an Age header in every non-first-hand
response.
I'd only support this change if it became:
An HTTP/1.1 cache MUST send an Age header in every response,
except that it MAY omit the Age header if the cache has
unambiguous proof that the response is firsthand, has not
flowed through any cache that is not compliant with HTTP/1.1,
and is not being transmitted to a client whose HTTP-Version
is less than 1.1.
but frankly, I think this is pointless. What's the cost of adding
the Age header, given that a compliant cache implementation MUST have
the code to add Age to non-first-hand responses anyway? It would
take far more code to check all of the necessary conditions.
Let's keep it simple.
-Jeff
Email: paulle@microsoft.com
Microsoft Phone: 1-206-882-8080
1 Microsoft Way Fax: 1-206-936-7329
Redmond, WA 98052
Received on Friday, 31 May 1996 14:27:41 UTC