Re: HTTP 1.0&1.1 URL safe characters conflict with HTML?

> "+" probably should be 'reserved' but not 'unsafe', because the
> meaning of the character encoded and not encoded is different.

More the merrier -- we should make "$" reserved as well, just so we
have a few extras lying around.

But, is this something we should change in HTTP or wait until it is
fixed in RFC 1738 + 1808?

 ...Roy T. Fielding
    Department of Information & Computer Science    (
    University of California, Irvine, CA 92717-3425    fax:+1(714)824-4056

Received on Saturday, 10 February 1996 21:32:54 UTC