Opened 10 years ago

Closed 10 years ago

Last modified 8 years ago

#151 closed editorial (fixed)

range unit missing from other-ranges-specifier in Range header

Reported by: julian.reschke@… Owned by: ylafon@…
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 10 years ago by ylafon@…

  • Owner set to ylafon@…
  • Priority set to normal
  • Type changed from design to editorial

comment:2 Changed 10 years ago by ylafon@…

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

Fixed in [637]:

Resolve #151: Fixed the grammar to require the range-unit "=" range-set syntax (closes #151)

comment:3 Changed 8 years ago by mnot@…

  • Severity changed from Candidate WG Document to Active WG Document
Note: See TracTickets for help on using tickets.