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

> Reviewing not quite current HTTP 1.0 and 1.1 drafts I noticed that the 
> plus sign (+) character is included as a safe character.
> This would seem to be in conflict with current practice and the HTML
> RFC where the + is part of the url encoding scheme to represent blanks.

It is safe, and "+" does not represent blanks.  The "+" character is
used to separate keywords in a URL generated by an ISINDEX query,
but those separators are not equivalent to blanks.  Since the query part
is generated, there is no need for "+" to be reserved in the URL syntax,
which is why it is not reserved in RFC 1738.

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

Received on Friday, 9 February 1996 15:38:15 UTC