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

Re: Comments on Byte range draft

From: Larry Masinter <masinter@parc.xerox.com>
Date: Mon, 13 Nov 1995 17:15:21 PST
To: montulli@mozilla.com
Cc: ietf-lists@proper.com, http-wg%cuckoo.hpl.hp.com@hplb.hpl.hp.com
Message-Id: <95Nov13.171527pst.2733@golden.parc.xerox.com>
Wait wait, I keep on saying "if-not-modified-since" and you keep on
replying "if-modified-since". 

Normally, GET with caching uses 'if-modified-since', i.e., give me the
data if it's newer than/different from what I already have.

However, GET of a byte range need the converse. It's "give me this
byte range of this object, UNLESS the object is newer than/different
from what I already have".

The sense is different. HTTP doesn't have a "if-not-modified-since",
and would need it if you want byte ranges to actually work with data
that might change.

  
Received on Monday, 13 November 1995 17:23:35 EST

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