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

Re: Improving If-Modified-Since

From: Larry Masinter <masinter@parc.xerox.com>
Date: Wed, 16 Aug 1995 15:22:02 PDT
To: montulli@mozilla.com
Cc: http-wg%cuckoo.hpl.hp.com@hplb.hpl.hp.com
Message-Id: <95Aug16.152203pdt.2763@golden.parc.xerox.com>
> It doesn't solve the problem of two dates being exactly the
> same but the file has been modified, or the problem of a file getting
> modified and having it's date set into the past.  Date's alone
> are not a strong enough versioning system.  And don't try and tell me 
> that these don't happen.  They are as likely to happen as a file with
> a date far forward, and these kinds of problems are happening all
> the time.

These problems happen, but they often happen in ways that preserve
length. If you want something stronger than date, then use a checksum;
if you're going to use a checksum, you might as well use MD5 or SHA.

Checksums can be pre-computed by the server and periodically
recomputed by them as well, sent along as content-md5 headers and just
sent back in HTTP/1.1 get-if-not-content-MD5 request.
Received on Wednesday, 16 August 1995 15:25:09 UTC

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