- From: Jeffrey Mogul <mogul@pa.dec.com>
- Date: Mon, 13 Jan 97 18:52:36 PST
- To: http-wg%cuckoo.hpl.hp.com@hplb.hpl.hp.com
Excerpted, from the IETF mailing list:
------- Forwarded Message
A New Internet-Draft is available from the on-line Internet-Drafts
directories.
Title : Forcing HTTP/1.1 proxies to revalidate responses
Author(s) : J. Mogul
Filename : draft-mogul-http-revalidate-00.txt
Pages : 10
Date : 01/07/1997
The HTTP/1.1 specification [1] currently defines a ``proxy-revalidate''
Cache-control directive, which forces a proxy to revalidate a stale
response before using it in a reply. There is no mechanism defined that
forces a proxy, but not an end-client, to revalidate a fresh response. The
lack of such a mechanism is due to an error in drafting RFC2068, and
appears to create problems for use of the Authorization header, the Digest
Access Authentication extension [2], the State Management Mechanism [3],
and several other proposed extensions. This document discusses the problem
and several possible solutions, and proposes to add a new ``proxy-maxage''
directive as the best available solution.
ftp://ds.internic.net/internet-drafts/draft-mogul-http-revalidate-00.txt
------- End of Forwarded Message
-Jeff
Received on Monday, 13 January 1997 19:00:53 UTC