Opened 13 years ago

Closed 13 years ago

Last modified 21 months ago

#152 closed design (duplicate)

range unit missing from other-ranges-specifier in Range header (dup)

Reported by: julian.reschke@… Owned by:
Priority: normal Milestone: unassigned
Component: p5-range Severity: Active WG Document
Keywords: Cc:

Description

In ​http://greenbytes.de/tech/webdav/draft-ietf-httpbis-p5-range-06.html#rfc.section.5.4.2, we have: 

  Range   = "Range" ":" OWS Range-v
  Range-v = byte-ranges-specifier
          / other-ranges-specifier
  other-ranges-specifier = 1*CHAR

Shouldn't other-ranges-specifier be something like: 

  other-ranges-specifier = other-range-unit "=" 1*CHAR

...so that a recipient can parse the unit name out of the header in a generic way?

Change History (3)

comment:1 Changed 13 years ago by julian.reschke@…

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

Removed as duplicate of #151.

comment:2 Changed 10 years ago by mnot@…

  • Priority set to normal
  • Severity changed from Candidate WG Document to Active WG Document

comment:3 Changed 21 months ago by mnot@…

  • Summary changed from range unit missing from other-ranges-specifier in Range header to range unit missing from other-ranges-specifier in Range header (dup)
Note: See TracTickets for help on using tickets.