Re: URL parsing--mayhap the wrong forum?

2006-04-20 Thread $Bill Luebkert
[EMAIL PROTECTED] wrote: > > Gentle Readers, > > Special thanks to $Bill, Josh, Jack, Bowie, Howard M. and Martin T. for > their efforts. It seems like my difficulty is not so much with Perl as > it is with IE and the registry. IE follows an obscure set of rules when > creating reg entries for T

URL parsing--mayhap the wrong forum?

2006-04-20 Thread Deane . Rothenmaier
Gentle Readers, Special thanks to $Bill, Josh, Jack, Bowie, Howard M. and Martin T. for their efforts. It seems like my difficulty is not so much with Perl as it is with IE and the registry. IE follows an obscure set of rules when creating reg entries for Trusted Sites. As an example, when      

Re: URL parsing

2006-04-19 Thread Petr Vileta
- Original Message - From: <[EMAIL PROTECTED]> To: Sent: Wednesday, April 19, 2006 5:04 PM Subject: URL parsing "foo.bar.com/ignore/this/". Maybe this $url = 'http://foo.bar.com/ignore/this/'; ($protocol,$remainder,@domain_parts)=tear_it_up($url); s

Re: URL parsing

2006-04-19 Thread Josh . Perlmutter
Deane- quick search of ICANN revealed a listing of the 2-letter domains http://www.iana.org/cctld/cctld-whois.htm and this information on the other TLDS source: http://icann.org/cctlds/ Traditionally, the agreement to implement coordinated policies for the Internet has been informal. As the In

Re: URL parsing

2006-04-19 Thread Josh . Perlmutter
Deane- My response is embedded. -Josh [EMAIL PROTECTED] wrote on 04/19/2006 12:46:24 PM: >1. URL parsing ([EMAIL PROTECTED]) > -- > > Message: 1 > Date: Wed, 19 Apr 2006 10:04:35 -0500 > From: [EMAIL PR

RE: URL parsing

2006-04-19 Thread Thurn, Martin
LY PLAIN TEXT email to mailing lists. - - Martin From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of [EMAIL PROTECTED] Sent: Wednesday, April 19, 2006 11:05 To: activeperl@listserv.ActiveState.com Subject: URL parsing

Re: URL parsing

2006-04-19 Thread $Bill Luebkert
[EMAIL PROTECTED] wrote: > > I'm doing some splitting of URLs, and things are getting more and more > complicated, what with suddenly needing to allow two, three, or even > four character TLDs (.us, .gov, .info). I originally thought I'd only > need to pass a few common threes--such as .com. > >

RE: URL parsing

2006-04-19 Thread Bowie Bailey
[EMAIL PROTECTED] wrote: > I'm doing some splitting of URLs, and things are getting more and > more complicated, what with suddenly needing to allow two, three, or > even four character TLDs (.us, .gov, .info). I originally thought I'd > only need to pass a few common threes--such as .com. > >

URL parsing

2006-04-19 Thread Deane . Rothenmaier
I'm doing some splitting of URLs, and things are getting more and more complicated, what with suddenly needing to allow two, three, or even four character TLDs (.us, .gov, .info). I originally thought I'd only need to pass a few common threes--such as .com. Is there a standard Perl library routi