W3C home > Mailing lists > Public > www-talk@w3.org > July to August 1996

Re: URL parsing and IPv6 addresses

From: Shel Kaphan <sjk@amazon.com>
Date: Wed, 7 Aug 1996 19:49:27 -0700 (PDT)
Message-Id: <199608080249.TAA15755@iguana.amazon.com>
To: Kim <bookwyrm@agii.solluna.org>
Cc: www-talk@w3.org
bookwyrm@agii.solluna.org writes:
 > Earlier, <Shel Kaphan> inscribed:
 > > 
 > > How about just using some other punctuation besides ":" before port numbers
 > > in URLs for IPv6, for example ";"?  Surely the URL parser is going to have
 > > to know whether it's an IPv4 or IPv6 IP address by the time it gets
 > > that far.
 > 
 > ";" would be a very bad character in my opinion - 
 >     "http://100.100.100.100;/bin/rm -rf /"
 > could cause a lot of problems in poorly written scripts that process
 > URLs.  Shell characters should be avoided as much as possible, I think.
 > 
 > I could live with the use of "." to separate the port in IPv6 addresses,
 > though it does allow "http://::131.247.108.14.80/", that is not an 
 > ambiguous representation.
 > 
 > Kim
 > 
 > 

Yes, ";" was not a good choice.  Several people have suggested solving
this by appropriate use of some character that doesn't bother
shells. So far dot (.) or comma (,) sound like the best choices.  (Is
there a common shell or scripting language that cares about comma?)
In any case it seems like some version of this solution (picking a
clear delimiter) involves the least amount of global disturbance.

--Shel
Received on Wednesday, 7 August 1996 22:49:47 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Wednesday, 27 October 2010 18:14:19 GMT