W3C home > Mailing lists > Public > ietf-http-wg@w3.org > July to September 2009

Re: Issue 152: range unit in Range header for custom ranges, was: issue 85 - range unit extensions

From: Yves Lafon <ylafon@w3.org>
Date: Tue, 28 Jul 2009 05:18:13 -0400 (EDT)
To: Julian Reschke <julian.reschke@gmx.de>
cc: HTTP Working Group <ietf-http-wg@w3.org>, Mark Nottingham <mnot@mnot.net>
Message-ID: <alpine.DEB.1.10.0907280516350.24967@wnl.j3.bet>
On Tue, 31 Mar 2009, Julian Reschke wrote:

> Julian Reschke wrote:
>> - Finally, in 
>> <http://greenbytes.de/tech/webdav/draft-ietf-httpbis-p5-range-06.html#rfc.section.5.4.2>, 
>> we have:
>>
>>   Range   = "Range" ":" OWS Range-v
>>   Range-v = byte-ranges-specifier
>>           / other-ranges-specifier
>>   other-ranges-specifier = 1*CHAR
>> 
>> Shouldn't other-ranges-specifier be something like:
>>
>>   other-ranges-specifier = other-range-unit "=" 1*CHAR
>> 
>> ...so that a recipient can parse the unit name out of the header in a 
>> generic way? (unless I'm missing something obvious, this should be tracked 
>> as a separate issue)
>
> Raised as <http://trac.tools.ietf.org/wg/httpbis/trac/ticket/152>.

Issue 151 (152 was a duplicate of it) was closed with the following 
changes:

>>   Range   = "Range" ":" OWS Range-v
>>   Range-v = byte-ranges-specifier
>>           / other-ranges-specifier
>>   other-ranges-specifier = 1*CHAR

=>

Range   = "Range" ":" OWS Range-v
Range-v = byte-ranges-specifier
           / other-ranges-specifier
other-ranges-specifier = other-range-unit "=" other-range-set
other-range-set = 1*CHAR

-- 
Baroula que barouleras, au tiéu toujou t'entourneras.

         ~~Yves
Received on Tuesday, 28 July 2009 09:18:25 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Friday, 27 April 2012 06:51:08 GMT