#2 closed editorial (fixed)
'unsafe' characters
Reported by: | mnot@… | Owned by: | fielding@… |
---|---|---|---|
Priority: | Milestone: | 01 | |
Component: | p1-messaging | Severity: | |
Keywords: | Cc: |
Description
In the rules for comparison of URIs [section 3.2.3], it says:
Characters other than those in the "reserved" and "unsafe" sets (see RFC 2396 [42]) are equivalent to their ""%" HEX HEX" encoding.
but RFC 2396 has no definition of a character set called "unsafe".
The paragraph should read:
Characters other than those in the "reserved" set (see RFC 2396 [42]) are equivalent to their ""%" HEX HEX" encoding.
This was an historical artifact. An earlier HTTP draft had defined a set of 'unsafe' characters, but they were characters that were not valid in a URI, so making a special case in the comparison rule was not needed.
Change History (4)
comment:1 Changed 15 years ago by fielding@…
- Milestone set to 01
- Owner set to fielding@…
- Status changed from new to assigned
comment:2 Changed 15 years ago by fielding@…
- Resolution set to fixed
- Status changed from assigned to closed
- version set to 00
comment:3 Changed 15 years ago by mnot@…
- version changed from 00 to d00
comment:4 Changed 15 years ago by julian.reschke@…
- Component set to p1-messaging
Note: See
TracTickets for help on using
tickets.
Fixed in [69]