UrlParse, TLD not consistent when TLD is like co.nz

[jimasun]

At public function parseHost($string) you assume that the TLD is the piece after the last period.

This assumption break in the case of sub.domain.com.af. One way to solve it is to check for valid values (co, com).

[maximkott]

Hi @jimasun

From my point of view af is the one and only tld in this url. It is wrong, obviously, but it is not the job of a url to validate tlds, domains and protocols. What would you expect to happen, that you get com as tld and af is thrown away?

[jimasun]

I would of course expect to get com.af as a valid suffix. Here is some info on the issue, which is a bit more complicated as the values of TLD need to be validated against a list: http://uri.thephpleague.com/5.0/components/host/#host-represented-by-a-registered-name

Also, here is the project that league URI is using https://github.com/jeremykendall/php-domain-parser

Thanks.

[maximkott]

Thank you for the links! I see your point. So basically it's about a new feature, like getPublicSuffix, since com.af is not a valid tld, but a tld with an extension / suffix.

I'll try to add this feature in the next few days.