W3C home > Mailing lists > Public > public-media-fragment@w3.org > September 2009

Re: Multiple Range headers in an HTTP request

From: Raphaël Troncy <Raphael.Troncy@cwi.nl>
Date: Thu, 10 Sep 2009 12:12:12 +0200
Message-ID: <4AA8D0FC.4060208@cwi.nl>
To: Yves Lafon <ylafon@w3.org>
CC: Philip Jägenstedt <philipj@opera.com>, Media Fragment <public-media-fragment@w3.org>
>> Apache 2.2:
>> A: Content-Range: bytes 0-99
>> B: Content-Range: bytes 0-99 (multipart)

So, B should be something like:

HTTP/1.1 206 Partial Content
Content-type: multipart/byteranges; boundary=A_SEPARATOR
--A_SEPARATOR
Content-type: video/mp4
Content-range: bytes 0-99/50000
--A_SEPARATOR
Content-type: video/mp4
Content-range: bytes 100-199/50000
--A_SEPARATOR--

>> C: Content-Range: bytes 0-99 (multipart)
>> D: 200 OK (full resource)
> 
> C and D should have been either full resource or the single byte 
> fragment, but not multipart.

Ah! Why? Because various units are mixed?

>> IIS 5.0:
>> A: Content-Range: bytes 0-99
>> B: 200 OK (full resource)
>> C: 200 OK (full resource)
>> D: 200 OK (full resource)
>>
>> Conclusion: completely broken with multiple Range headers.
> Well, no that's perfectly valid to answer with the full resource when 
> mutiple ranges are requested.

 From the latest HTTPBis draft you have sent, it is written:

"A response to a request for multiple ranges, whose result is a single 
range, MAY be sent as a multipart/byteranges media type with one part.".

So is it expected that the server does some clever processing of the 
various bytes range requested and actually determine whether they cover 
or not the same portion?
You might answer that the server "MAY" do this clever processing :-)

   Raphaël

-- 
Raphaël Troncy
EURECOM, Multimedia Communications Department
2229, route des Crêtes, 06560 Sophia Antipolis, France.
e-mail: raphael.troncy@eurecom.fr & raphael.troncy@gmail.com
Tel: +33 (0)4 - 9300 8242
Fax: +33 (0)4 - 9000 8200
Web: http://www.cwi.nl/~troncy/
Received on Thursday, 10 September 2009 10:13:16 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Wednesday, 21 September 2011 12:13:34 GMT