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

Re: Section 14.36 Range, and PUTs

From: Larry Masinter <masinter@parc.xerox.com>
Date: Sat, 1 Jun 1996 11:47:26 PDT
To: fielding@liege.ICS.UCI.EDU
Cc: paulle@microsoft.com, http-wg%cuckoo.hpl.hp.com@hplb.hpl.hp.com
Message-Id: <96Jun1.114732pdt.2733@golden.parc.xerox.com>
X-Mailing-List: <http-wg@cuckoo.hpl.hp.com> archive/latest/696
Roy said (about Range on PUT):

> I think you are missing something.  Range is a request header that
> applies to the entity returned as the result of the request.  I could
> understand sending Content-Range in a PUT request (which would have
> the effect of putting just a range of an entity), though I wouldn't
> suggest it for 1.1.

Yes. Maybe this (well, just the description of "Range is a request
header that applies to the entity returned as the result of the
request") just belongs in the description of the Range header.

I actually can now see a use for Range with POST:

You do a query using POST, it returns megabytes, and you want to retry
the query; the results were returned with a strong entity ID, so this
actually makes sense.

Thanks, Roy, for saying this clearly.

-  Larry
Received on Saturday, 1 June 1996 11:52:54 UTC

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