W3C home > Mailing lists > Public > ietf-http-wg@w3.org > April to June 2012

Re: Review of draft-ietf-httpbis-p5-range-19.txt

From: Amos Jeffries <squid3@treenet.co.nz>
Date: Wed, 09 May 2012 13:19:51 +1200
To: <ietf-http-wg@w3.org>
Message-ID: <83bf68ec95364b4e8f0f45be25c3b3a1@treenet.co.nz>
On 09.05.2012 08:02, Alexey Melnikov wrote:
> Hi,
> Another late review:


> 5.2.  Content-Range
>      byte-range-resp-spec    = (first-byte-pos "-" last-byte-pos)
>                              / "*"
>      instance-length         = 1*DIGIT
> Are leading zeroes allowed? (I.e. would an implementation that just
> treat these values as strings be Ok?) But more importantly:
>  Is there a maximum limit on this value? Is 128bit unsigned value Ok?
>  Is there a minimum size any implementation need to support? Is 8bit 
> Ok?

That is implementation specific detail. Pick your limit and if the 
range value exceeds it they could still be perfectly valid, just relay 
without local handling. HTTP does not have to impose any restrictions 

For example, there are range requests floating around the Internet for 
TB and PB sized objects. But systems with local 32-bit limits are still 
able to relay them when implemented correctly.

Received on Wednesday, 9 May 2012 01:20:21 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 17:14:00 UTC