W3C home > Mailing lists > Public > www-html@w3.org > April 2000

Re: URLencoding.

From: Nir Dagan <nir@nirdagan.com>
Date: Thu, 06 Apr 2000 23:38:18 -0400
Message-Id: <>
To: "Dave Bridger" <dbridger@inlink.com>, <www-html@w3.org>
You may prefer to check out the 
latest URI syntax RFC http://www.ietf.org/rfc/rfc2396.txt
It is very clear on the hex escaping issue. Also there are 
some changes from RFC1738.

Nir Dagan

At 10:24 PM 4/6/00 -0500, Dave Bridger wrote:
>I am attempting to determine exactly which special characters should be escaped
>to Hex and which should not be escaped during urlencoding. The HTML 4.01
>Specification is very unclear and RFC1738 does not help at all. The mailing list
>archive produces only a partial thread which only partly help to clarify the
>A quick Web search indicates that others are also not clear about urlencoding.
>The prevailing practice seems to be to escape everything except alphanumerics
>and space which becomes +. For example, see the JAVA urlencoding class at:
>Fortunately RFC1738 is permissive so the overencoding practice will not harm
>Can anyone give me a definitive answer as to which characters need not be
>Perhaps Section 17.3.4 of the HTML Spec should be clarified.

Nir Dagan
Assistant Professor of Economics
Brown University 
Providence, RI

Received on Thursday, 6 April 2000 23:36:06 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 7 January 2015 15:05:53 UTC