W3C home > Mailing lists > Public > ietf-http-wg@w3.org > January to March 2013

Re: #407: draft-ietf-httpbis-p5-range-21, "3.2 416 Requested Range Not Satisfiable"

From: Yves Lafon <ylafon@w3.org>
Date: Mon, 7 Jan 2013 05:53:42 -0500 (EST)
To: Mark Nottingham <mnot@mnot.net>
cc: Julian Reschke <julian.reschke@gmx.de>, ietf-http-wg@w3.org
Message-ID: <alpine.DEB.1.10.1301070537180.16025@wnl.j3.bet>
On Thu, 15 Nov 2012, Mark Nottingham wrote:

> Now <http://trac.tools.ietf.org/wg/httpbis/trac/ticket/407>
> On 24/10/2012, at 11:21 PM, Julian Reschke <julian.reschke@gmx.de> wrote:
>> <http://greenbytes.de/tech/webdav/draft-ietf-httpbis-p5-range-21.html#status.416>:
>> "When this status code is returned for a byte-range request, the 
>> response SHOULD include a Content-Range header field specifying the 
>> current length of the representation (see Section 5.2). This response 
>> MUST NOT use the multipart/byteranges content-type. For example,"
>> What is this "MUST NOT" about? Are there clients that will ignore the 
>> status code and assume success if they see the expected content-type?

If a multipart/byteranges can be sent in response to a 416, it can also be 
send in response to a 200, or to a 206.
In the case of a 206, you will have a Content-Range in the response and in 
the multipart/byteranges package, so it will be a partial response of a 
partial response without asking for it. (the restriction is also there for 
206, see discussion around #405).

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

Received on Monday, 7 January 2013 10:53:46 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 1 March 2016 11:11:09 UTC