* WGs marked with an * asterisk has had at least one new draft made available during the last 5 days

Ticket #407 (closed design: fixed)

Opened 22 months ago

Last modified 16 months ago

416 and multipart/byteranges

Reported by: mnot@pobox.com Owned by:
Priority: normal Milestone: 22
Component: p5-range Severity: In WG Last Call
Keywords: Cc:
Origin: http://www.w3.org/mid/5087DD2F.7000303@gmx.de

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

comment:1 Changed 21 months ago by mnot@pobox.com

  • Owner draft-ietf-httpbis-p5-range@tools.ietf.org deleted

comment:2 Changed 19 months ago by mnot@pobox.com

[2066] removed this requirement.

comment:3 Changed 19 months ago by mnot@pobox.com

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

comment:4 Changed 18 months ago by mnot@pobox.com

  • Milestone changed from unassigned to 22

comment:5 Changed 16 months ago by mnot@pobox.com

  • Status changed from closed to reopened
  • Resolution incorporated deleted

comment:6 Changed 16 months ago by mnot@pobox.com

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