W3C home > Mailing lists > Public > ietf-http-wg-old@w3.org > May to August 1996

RE: EDITS for Section 13.20 (Cache Replacement for Varying Resources)

From: Paul Leach <paulle@microsoft.com>
Date: Thu, 2 May 1996 09:37:37 -0700
Message-Id: <c=US%a=_%p=msft%l=RED-77-MSG-960502163737Z-33362@abash1.microsoft.com>
To: "'Roy T. Fielding'" <fielding@avron.ICS.UCI.EDU>
Cc: "'koen@win.tue.nl'" <koen@win.tue.nl>, "'http-wg%cuckoo.hpl.hp.com@hplb.hpl.hp.com'" <http-wg%cuckoo.hpl.hp.com@hplb.hpl.hp.com>


>----------
>From: 	Roy T. Fielding[SMTP:fielding@avron.ICS.UCI.EDU]
>Sent: 	Thursday, May 02, 1996 2:12 AM
>To: 	Paul Leach
>Cc: 	'koen@win.tue.nl'; http-wg%cuckoo.hpl.hp.com@hplb.hpl.hp.com
>Subject: 	Re: EDITS for Section 13.20 (Cache Replacement for Varying
>Resources) 
>
>>>   13.20 Caching Responses
>>>
>>    If a new cacheable response (see sections 10.7.2, 13.11.2, 13.11.3
>>>and 13.14) 
>>    is received from a non-varying resource while an old response for the
>> same 
>>    resource is cached, the cache SHOULD insert the new response into
>> cache storage 
>>    (see section 13.7.3).
>
>Not accurate -- the cache never needs to do any such thing in order to
>remain conditionally compliant with HTTP (the meaning of "SHOULD").

If it doesn't cache responses as a general rule, it may be a proxy, but
it ain't a cache.
>
Received on Thursday, 2 May 1996 09:46:04 EDT

This archive was generated by hypermail pre-2.1.9 : Wednesday, 24 September 2003 06:31:59 EDT