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

Ticket #319 (closed design: fixed)

Opened 3 years ago

Last modified 3 years ago

case sensitivity of ranges in p5

Reported by: ylafon@w3.org Owned by: draft-ietf-httpbis-p5-range@tools.ietf.org
Priority: normal Milestone: 17
Component: p5-range Severity: Active WG Document
Keywords: Cc:
Origin:

Description

Currently, all of the range units are defined as BNF Tokens, which means that they're case-insensitive.

Clarifying that they are indeed case-insensitive in plain text, as well as other parts reusing BNF's Token or String construct.

Change History

comment:2 Changed 3 years ago by julian.reschke@gmx.de

From [1461]:

tuning (see #319)

comment:3 Changed 3 years ago by mnot@pobox.com

Yves, can this be marked incorporated?

comment:4 Changed 3 years ago by julian.reschke@gmx.de

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

comment:5 Changed 3 years ago by julian.reschke@gmx.de

-17 says "closed", so yes, this can be marked as resolved incorporated.

comment:6 Changed 3 years ago by julian.reschke@gmx.de

  • Milestone changed from unassigned to 17

comment:7 Changed 3 years ago by mnot@pobox.com

  • Status changed from closed to reopened
  • Resolution incorporated deleted

comment:8 Changed 3 years ago by mnot@pobox.com

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