Purl cannot parse some Blogspot sudomains.

[Aristona]

Hi,

While those work fine:

http://anil.blogspot.com.tr :: $purl->subdomain is "anil"
http://anil.blogspot.com :: $purl->subdomain is "anil"

Those domain extensions doesn't work:

http://anil.blogspot.co.uk :: $purl->subdomain is NULL
http://anil.blogspot.nl :: $purl->subdomain is NULL
http://anil.blogspot.in :: $purl->subdomain is NULL

Could be a bug.

Is there any way I can extend domain extensions list for Blogspot and allow those domain extensions too?

[peter279k]

This issue is happened by this line and this is the php-domain-parser package.
You should submit the issue for the php-domain-parser.

After upgrade that package version to 3.0 version, this issue has been existed.
Here is my code I run:

<?php

require_once 'vendor/autoload.php';

$pslManager = new Pdp\PublicSuffixListManager();
$parser = new Pdp\Parser($pslManager->getList());

$host = 'http://anil.blogspot.co.uk';
$url = $parser->parseUrl($host);
var_dump($url);

[jwage]

Should we stop using that package? I don't think it is being maintained.

[peter279k]

@jwage , do you mean we stop using the php-domain-parser package?

[jwage]

Yes, we would have to bring what it does in house. I'm not sure if it makes sense.

[peter279k]

We can use another parser package to replace the php-domain-parser package.
How about refering this one?
What do you think?

Thanks.

[jwage]

@peter279k That package is fully featured? I think we only use php-domain-parser for a very small piece of functionality so I don't think it makes sense to pull in a big library like that. What if we just pull the small bit of functionality we depend on php-domain-parser for back in to Purl?

[jeremykendall]

PHP Domain Parser is under active maintenance. If you’re having issues with parsing please make sure the public suffix list cache is up to date. If that doesn’t solve the issue please open an issue against the parser so we can get it taken care of. Thanks!

[jeremykendall]

By parsing, the domain parser only helps identify component parts of a URL: sub domain, domain, and registrable domain. It is definitely not a full featured URL parser. It’s intended as a complement to purl.

[peter279k]

@jeremykendall, thank you for your reply.
I appreciate that explanation and I think the domain, and sub domain should be implemented by purl.
How about opening another issue about this, @jwage ?

[jeremykendall]

@peter279k I highly recommend doing a bit of research about URL parsing before deciding to attempt to implement it yourself. Regex won't cut it. I'm not saying you shouldn't, and switching from php-domain-parser might be the best for the project, but it's a topic that's fairly complex and should be well considered before making a decision to reimplement the functionality.

[jwage]

@jeremykendall Thanks for chiming in. @peter279k Lets open an issue on php-domain-parser and see if we can get it fixed there.