Skip Menu |

This queue is for tickets about the ParseUtil-Domain CPAN distribution.

Report information
The Basics
Id: 105459
Status: resolved
Priority: 0/
Queue: ParseUtil-Domain

People
Owner: Nobody in particular
Requestors: Mayur_Kulkarni [...] symantec.com
Cc:
AdminCc:

Bug Information
Severity: (no value)
Broken in: (no value)
Fixed in: (no value)



Subject: FW: ParseUtil-Domain-2.411 and 'com.se'
Date: Wed, 24 Jun 2015 01:27:30 -0700
To: "bug-ParseUtil-Domain [...] rt.cpan.org" <bug-ParseUtil-Domain [...] rt.cpan.org>
From: Mayur Kulkarni <Mayur_Kulkarni [...] symantec.com>
Hello, We are trying to use version ParseUtil-Domain-2.411 to parse a domain with tld 'com.se'. We are not able to extract the tld and the domain name using the suffix list provided with the latest version of the module. I think that we first need to use the latest suffix list and then make changes to the tld_regex to get the com.se to be extracted correctly. Questions: 1. We need the suffix lists to be updated in the ConfigData.pm. Is there a way to modify the tld regex as we see changes in the https://publicsuffix.org/list/ on our side? 2. If there is no good way from our side to make these changes, will you be able to update the config to get the recent new tlds added? Please let me know if you have questions. Thanks Show quoted text
________________________________ Mayur Kulkarni Software Engineer, Star Technology & Response Symantec Corporation www.symantec.com<http://www.symantec.com/> Office: +91 20 67154244 Mobile: +91 9371290112 mayur_kulkarni@symantec.com<mailto:mayur_kulkarni@symantec.com> [cid:image003.png@01D0AE82.2F3490E0]
Download image003.png
image/png 5.9k
image003.png
On Wed Jun 24 04:28:01 2015, Mayur_Kulkarni@symantec.com wrote: Show quoted text
> Hello, > > We are trying to use version ParseUtil-Domain-2.411 to parse a domain > with tld 'com.se'. We are not able to extract the tld and the domain > name using the suffix list provided with the latest version of the > module. I think that we first need to use the latest suffix list and > then make changes to the tld_regex to get the com.se to be extracted > correctly. > > Questions: > > 1. We need the suffix lists to be updated in the ConfigData.pm. > Is there a way to modify the tld regex as we see changes in the > https://publicsuffix.org/list/ on our side? > > 2. If there is no good way from our side to make these changes, > will you be able to update the config to get the recent new tlds > added? > > Please let me know if you have questions. > > Thanks > ________________________________ > Mayur Kulkarni > Software Engineer, Star Technology & Response > Symantec Corporation > www.symantec.com<http://www.symantec.com/> > > Office: +91 20 67154244 > Mobile: +91 9371290112 > > mayur_kulkarni@symantec.com<mailto:mayur_kulkarni@symantec.com> > > > [cid:image003.png@01D0AE82.2F3490E0]
Hi Mayur I've updated the regex with the latest from the suffix list. I've also added a script called "suffix-regex.pl" that uses the code I originally wrote to produce the actual regex by parsing the suffix list. It just parses the file and prints out the generated regex. This should enable you to generate an updated regex whenever you want and replace the one in ParseUtil::Domain::ConfigData::tld_regex. You can just create a local lib/ParseUtil/Domain/ConfigData.pm in your PERL5PATH and add a subroutine sub tld_regex { return qr{ <new regex here> }x; } Be aware though, that the current public suffix list is missing a lot of nTLDs.
Subject: RE: [rt.cpan.org #105459] FW: ParseUtil-Domain-2.411 and 'com.se'
Date: Fri, 26 Jun 2015 02:15:17 -0700
To: "bug-ParseUtil-Domain [...] rt.cpan.org" <bug-ParseUtil-Domain [...] rt.cpan.org>
From: Mayur Kulkarni <Mayur_Kulkarni [...] symantec.com>
Hi William, Thank you for the change and the extra script. That helped a lot. This ticket can now be closed. I also had another ticket opened for the same module and problem for that case was solved after an upgrade. https://rt.cpan.org/Public/Bug/Display.html?id=93559 this ticket can also be closed. Thanks Mayur Kulkarni Show quoted text
-----Original Message----- From: William Travis Holton via RT [mailto:bug-ParseUtil-Domain@rt.cpan.org] Sent: Thursday, June 25, 2015 3:07 AM 3 To: Mayur Kulkarni Subject: [rt.cpan.org #105459] FW: ParseUtil-Domain-2.411 and 'com.se' <URL: https://rt.cpan.org/Ticket/Display.html?id=105459 > On Wed Jun 24 04:28:01 2015, Mayur_Kulkarni@symantec.com wrote:
> Hello, > > We are trying to use version ParseUtil-Domain-2.411 to parse a domain > with tld 'com.se'. We are not able to extract the tld and the domain > name using the suffix list provided with the latest version of the > module. I think that we first need to use the latest suffix list and > then make changes to the tld_regex to get the com.se to be extracted > correctly. > > Questions: > > 1. We need the suffix lists to be updated in the ConfigData.pm. > Is there a way to modify the tld regex as we see changes in the > https://publicsuffix.org/list/ on our side? > > 2. If there is no good way from our side to make these changes, > will you be able to update the config to get the recent new tlds > added? > > Please let me know if you have questions. > > Thanks > ________________________________ > Mayur Kulkarni > Software Engineer, Star Technology & Response Symantec Corporation > www.symantec.com<http://www.symantec.com/> > > Office: +91 20 67154244 > Mobile: +91 9371290112 > > mayur_kulkarni@symantec.com<mailto:mayur_kulkarni@symantec.com> > > > [cid:image003.png@01D0AE82.2F3490E0]
Hi Mayur I've updated the regex with the latest from the suffix list. I've also added a script called "suffix-regex.pl" that uses the code I originally wrote to produce the actual regex by parsing the suffix list. It just parses the file and prints out the generated regex. This should enable you to generate an updated regex whenever you want and replace the one in ParseUtil::Domain::ConfigData::tld_regex. You can just create a local lib/ParseUtil/Domain/ConfigData.pm in your PERL5PATH and add a subroutine sub tld_regex { return qr{ <new regex here> }x; } Be aware though, that the current public suffix list is missing a lot of nTLDs.