Opened 11 years ago
Closed 11 years ago
#319 closed design (fixed)
case sensitivity of ranges in p5
Reported by: | ylafon@… | Owned by: | draft-ietf-httpbis-p5-range@… |
---|---|---|---|
Priority: | normal | Milestone: | 17 |
Component: | p5-range | Severity: | Active WG Document |
Keywords: | Cc: |
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 (8)
comment:1 Changed 11 years ago by ylafon@…
comment:2 Changed 11 years ago by julian.reschke@…
comment:3 Changed 11 years ago by mnot@…
Yves, can this be marked incorporated?
comment:4 Changed 11 years ago by julian.reschke@…
- Resolution set to incorporated
- Status changed from new to closed
comment:5 Changed 11 years ago by julian.reschke@…
-17 says "closed", so yes, this can be marked as resolved incorporated.
comment:6 Changed 11 years ago by julian.reschke@…
- Milestone changed from unassigned to 17
comment:7 Changed 11 years ago by mnot@…
- Resolution incorporated deleted
- Status changed from closed to reopened
comment:8 Changed 11 years ago by mnot@…
- Resolution set to fixed
- Status changed from reopened to closed
Note: See
TracTickets for help on using
tickets.
See http://trac.tools.ietf.org/wg/httpbis/trac/changeset/1456