[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [idn] nameprep forbidden characters
- To: idn@ops.ietf.org
- Subject: Re: [idn] nameprep forbidden characters
- From: Alan Barrett <apb@cequrux.com>
- Date: Sun, 17 Sep 2000 14:21:45 +0200 (SAST)
- Delivery-date: Sun, 17 Sep 2000 05:24:26 -0700
- Envelope-to: idn-data@psg.com
On Sun, 17 Sep 2000, Adam M. Costello wrote:
> When I type http://foo:80/ into my browser, should it interpret that
> as host foo port 80, or as an internationalized host name containing a
> colon? How would I specify the other?
Colons are special characters in URIs, so if you wanted to specify
a hostname containing a colon, you would have to use an escape like
http://foo%3A80/.
Many currently deployed browsers undo %hex encoding at the wrong level
of parsing, and would (incorrectly) treat http://foo%3A80/ just like
http://foo:80/.
--apb (Alan Barrett)