[
https://issues.apache.org/jira/browse/VALIDATOR-216?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ben Speakmon resolved VALIDATOR-216.
------------------------------------
Resolution: Fixed
This has been addressed in the new UrlValidator. I chose not to use the
interface constant pattern as suggested, as that's frowned upon; rather, the
domains are stored in private static final List fields inside UrlValidator for
maximum flexibility.
We will need to update UrlValidator as new domains comes out in any case, but
since that happens only every couple of years, a configurable TLD mechanism
seemed like overkill.
> UrlValidator rejects top-level domains (TLDs) with more than 4 characters
> -------------------------------------------------------------------------
>
> Key: VALIDATOR-216
> URL: https://issues.apache.org/jira/browse/VALIDATOR-216
> Project: Commons Validator
> Issue Type: Bug
> Affects Versions: 1.3.1 Release
> Reporter: Kenji Matsuoka
> Assignee: Niall Pemberton
> Priority: Minor
> Fix For: 1.4
>
> Attachments: TLDConstants.java
>
>
> org.apache.commons.validator.UrlValidator#isValidAuthority rejects top-level
> domains (TLDs) with more than four characters. There are now at least two
> TLDs with more characters, .museum and .travel.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
