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

Ticket #2 (closed editorial: fixed)

Opened 7 years ago

Last modified 7 years ago

'unsafe' characters

Reported by: mnot@pobox.com Owned by: fielding@gbiv.com
Priority: Milestone: 01
Component: p1-messaging Severity:
Keywords: Cc:
Origin:

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

comment:1 Changed 7 years ago by fielding@gbiv.com

  • Owner set to fielding@gbiv.com
  • Status changed from new to assigned
  • Milestone set to 01

comment:2 Changed 7 years ago by fielding@gbiv.com

  • Status changed from assigned to closed
  • version set to 00
  • Resolution set to fixed

Fixed in [69]

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

  • version changed from 00 to d00

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

  • Component set to p1-messaging
Note: See TracTickets for help on using tickets.