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)
- Re: [idn] nameprep forbidden characters Kenneth Whistler
- RE: [idn] nameprep forbidden characters Jonathan Rosenne
- Re: [idn] nameprep forbidden characters James Seng
- Re: [idn] nameprep forbidden characters Dave Crocker
- Re: [idn] nameprep forbidden characters Patrik F�ltstr�m
- Re: [idn] nameprep forbidden characters Paul Hoffman / IMC
- Re: [idn] nameprep forbidden characters James Seng
- Re: [idn] nameprep forbidden characters Adam M. Costello
- Re: [idn] nameprep forbidden characters Patrik F�ltstr�m
- Re: [idn] nameprep forbidden characters Adam M. Costello
- Re: [idn] nameprep forbidden characters Alan Barrett
- Re: [idn] nameprep forbidden characters Mark Davis
- Re: [idn] nameprep forbidden characters Martin J. Duerst
