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

On Wed, 24 Oct 2012, Julian Reschke wrote:

> <>:
> "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.


Received on Thursday, 15 November 2012 10:37:36 UTC