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

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

From: Mark Nottingham <mnot@mnot.net>
Date: Thu, 15 Nov 2012 17:07:16 +1100
Cc: ietf-http-wg@w3.org
Message-Id: <14525785-453B-4F7A-8803-2475FADA28DD@mnot.net>
To: Julian Reschke <julian.reschke@gmx.de>
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?
> 
> Best regards, Julian
> 

--
Mark Nottingham   http://www.mnot.net/
Received on Thursday, 15 November 2012 06:07:44 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Thursday, 15 November 2012 06:07:45 GMT