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

caching vs revalidation in http1.1

From: Daniel Hellerstein <danielh@mailbox.econ.ag.gov>
Date: Mon, 04 May 1998 15:44:54 -0400
Message-Id: <s54de2a5.029@MAILBOX.ECON.AG.GOV>
To: http-wg@cuckoo.hpl.hp.com
X-Mailing-List: <http-wg@cuckoo.hpl.hp.com> archive/latest/104
There may be cases where an origin server has semi-permanent
resources (that change every few hours or days).  If these change
irregularly, allowing proxies to cache this may be problemmatic (i.e.;
one can not know a proper maxage value)

A second best solution would be to allow proxies to cache, but
insist they perform a conditional get (an If-modified of If-no-match)
before using the cached item.

rom my reading of the ver 3 spec, there's no way of doing this
("must-revalidate" sounds like it should, but it's really a "stale" modifier).

Am I missing something, or is there a notion that well designed caches
will make such an option unnecessary, or ....
Received on Monday, 4 May 1998 12:49:04 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 7 January 2015 14:40:22 UTC