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 11:36:56 +0200
Message-ID: <4AA8C8B8.5060404@cwi.nl>
To: Philip Jägenstedt <philipj@opera.com>
CC: Media Fragment <public-media-fragment@w3.org>, Yves Lafon <ylafon@w3.org>, Kilroy.Hughes@microsoft.com
Hi Philip

> I don't know what the specs say, but I did a little experiment with nc 
> (netcat):

Thanks for the tests! During a previous chat with Yves, he told me that 
it is fine w.r.t. the spec to have multiple Range headers, and indeed, 
the answer should be a mime multipart. However, it is a pain to 
implement :-( It is also fine to have multiple Range headers in 
different units, but until now, there is only one unit (bytes) 
implemented :-)

Regarding your tests:

> A:
> Range: bytes=0-99
> 
> B:
> Range: bytes=0-99
> Range: bytes=100-199
> 
> C:
> Range: bytes=0-99
> Range: seconds=10-20
> 
> D:
> Range: seconds=10-20
> Range: bytes=0-99
> 
> Apache 2.2:
> A: Content-Range: bytes 0-99
> B: Content-Range: bytes 0-99 (multipart)

Shouldn't be:
B: Content-Range: bytes 0-199 (multipart) ?

> C: Content-Range: bytes 0-99 (multipart)
> D: 200 OK (full resource)

D is interesting. If Apache does not understand the first Range header, 
then it ignores the following ones?

> IIS 5.0:
> A: Content-Range: bytes 0-99
> B: 200 OK (full resource)
> C: 200 OK (full resource)
> D: 200 OK (full resource)

I'm not really surprised of the IIS 5.0 behavior.
Kilroy, since you're listening to this list, would you like to comment 
on this test? Is it purposely that IIS does not implement the case where 
a HTTP request contains multiple Range headers?
Cheers.

   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 09:38:04 GMT

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