416 and multipart/byteranges

mnot commented 11 years ago

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?

Reported by @mnot, migrated from https://trac.ietf.org/trac/httpbis/ticket/407

mnot commented 11 years ago

@mnot changed owner from draft-ietf-httpbis-p5-range@tools.ietf.org to ``

mnot commented 11 years ago

@mnot commented:

2066 removed this requirement.

mnot commented 11 years ago

@mnot changed resolution to incorporated
@mnot changed status from new to closed

mnot commented 11 years ago

@mnot changed milestone from unassigned to 22

mnot commented 11 years ago

@mnot changed resolution from incorporated to ``
@mnot changed status from closed to reopened

mnot commented 11 years ago

@mnot changed resolution to fixed
@mnot changed status from reopened to closed

httpwg / httpbis-issues

416 and multipart/byteranges #407