W3C home > Mailing lists > Public > ietf-http-wg-old@w3.org > September to December 1997


From: Ben Laurie <ben@algroup.co.uk>
Date: Fri, 05 Sep 1997 20:13:06 +0100
Message-Id: <341059C2.BA71E853@algroup.co.uk>
To: Jim Gettys <jg@pa.dec.com>
Cc: http-wg%cuckoo.hpl.hp.com@hplb.hpl.hp.com
X-Mailing-List: <http-wg@cuckoo.hpl.hp.com> archive/latest/4340
Jim Gettys wrote:
> To close out this issue
> (http://www.w3.org/Protocols/HTTP/Issues/#DATE_IF_MODIFIED), I suggest the
> following note to be added to section 14.24 If-Modified-Since"
> "Note: An HTTP client should expect that If-Modified-Since headers sent
> for cache validation will be interpreted as
> 'If-Modification-date-does-not-match-exactly'. In other words, an HTTP client
> should preserve all of the accuracy in the Last-Modified date, rather than
> (perhaps) playing games based on the official semantics of If-Modified-Since."
> Let me know if there are any complaints.

If cache loops exist, this would allow the possibility of a perpetually
cached stale copy. I don't know if this is a real-world concern, though.



Ben Laurie            |Phone: +44 (181) 994 6435|Apache Group member
Freelance Consultant  |Fax:   +44 (181) 994 6472|http://www.apache.org
and Technical Director|Email: ben@algroup.co.uk |Apache-SSL author
A.L. Digital Ltd,     |http://www.algroup.co.uk/Apache-SSL
London, England.      |"Apache: TDG" http://www.ora.com/catalog/apache
Received on Friday, 5 September 1997 12:17:14 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 17:16:28 UTC