Ticket #2 (closed editorial: fixed)
|Reported by:||email@example.com||Owned by:||firstname.lastname@example.org|
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 ) 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 ) 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.
- Owner set to email@example.com
- Status changed from new to assigned
- Milestone set to 01
- Status changed from assigned to closed
- version set to 00
- Resolution set to fixed