httpbis: Ticket #2: 'unsafe' characters

Link:  http://trac.tools.ietf.org/wg/httpbis/trac/ticket/2

Component: p1-messaging

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.

Mails

• The "unsafe" charset Robert Brewer (fumanchu@aminus.org) (2008-06-28)
  • Re: The "unsafe" charset Henrik Nordstrom (henrik@henriknordstrom.net) (2008-06-28)
  • Re: The "unsafe" charset #2 Julian Reschke (julian.reschke@gmx.de) (2008-06-28)

Associated Checkins

fielding@gbiv.com (Sat, 22 Dec 2007 00:03:05 GMT)

[69]: Resolve #2: 'unsafe' characters

History

: comment added; owner, milestone set; status changed (Fri, 21 Dec 2007 22:52:57 GMT)

• owner set to fielding@gbiv.com
• status changed from new to assigned.
• milestone set to 01

: comment added; version, resolution set; status changed (Sat, 22 Dec 2007 00:03:05 GMT)

• status changed from assigned to closed.
• version set to 00
• resolution set to fixed

Fixed in [69]

: comment added; version changed (Sat, 22 Dec 2007 04:10:31 GMT)

• version changed from 00 to d00.

: comment added; component set (Sat, 09 Aug 2008 12:53:02 GMT)

• component set to p1-messaging

Related Information

Issues List Index