Opened 10 years ago

Closed 9 years ago

#407 closed design (fixed)

416 and multipart/byteranges

Reported by: mnot@… Owned by:
Priority: normal Milestone: 22
Component: p5-range Severity: In WG Last Call
Keywords: Cc:

Description

<​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?

Change History (6)

comment:1 Changed 10 years ago by mnot@…

  • Owner draft-ietf-httpbis-p5-range@… deleted

comment:2 Changed 9 years ago by mnot@…

[2066] removed this requirement.

comment:3 Changed 9 years ago by mnot@…

  • Resolution set to incorporated
  • Status changed from new to closed

comment:4 Changed 9 years ago by mnot@…

  • Milestone changed from unassigned to 22

comment:5 Changed 9 years ago by mnot@…

  • Resolution incorporated deleted
  • Status changed from closed to reopened

comment:6 Changed 9 years ago by mnot@…

  • Resolution set to fixed
  • Status changed from reopened to closed
Note: See TracTickets for help on using tickets.