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

Re: Media Fragments spec and HTTP

From: Adrien de Croy <adrien@qbik.com>
Date: Thu, 12 May 2011 19:56:31 +1200
Message-ID: <4DCB92AF.6040701@qbik.com>
To: Mark Nottingham <mnot@mnot.net>, HTTP Working Group <ietf-http-wg@w3.org>

On 12/05/2011 6:25 p.m., Mark Nottingham wrote:
>    Range: t:npt=10-20;include-setup

sheer madness.

Why can't they use some other header?  Or put the pagination into the 
URI so it can be cached?

IMO it was always an awful idea to even contemplate other range units.

* Content-Length can't be specified in other units.
* Chunk headers can only be bytes.

Framing is in bytes.

So it doesn't make sense to use anything other than bytes for Range.  
Anything else becomes opaque to any intermediary (good-bye 
cachability).  Furthermore Range is commonly stripped from requests by 
intermediaries that need the whole resource (e.g. for scanning).


Adrien de Croy - WinGate Proxy Server - http://www.wingate.com
Received on Thursday, 12 May 2011 07:57:09 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 17:13:52 UTC