- From: Yves Lafon <ylafon@w3.org>
- Date: Thu, 15 Nov 2012 05:37:35 -0500 (EST)
- To: Julian Reschke <julian.reschke@gmx.de>
- cc: ietf-http-wg@w3.org
On Wed, 24 Oct 2012, Julian Reschke 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?
It was present also in rfc2616, so nothing new. This is to enforce the
fact that multipart/byteranges contains a Content-Range header for each
part; An extra Content-Range would be like having two C-R with different
values, an error.
--
Baroula que barouleras, au tiéu toujou t'entourneras.
~~Yves
Received on Thursday, 15 November 2012 10:37:36 UTC