Lookalike URLs: Do not trigger when the eTLD+1 of the navigated domain is not IDN
The top domain heuristic incorrectly marks certain domains as lookalikes, despite the fact that the domain itself is a top domain. As a result of this bug, tést[.]blogspot[.]com displays a "Did you mean to go to blogspot.com". This happens because: - We currently use INCLUDE_PRIVATE_REGISTRIES flag when computing eTLD+1s via net::registry_controlled_domains::GetDomainAndRegistry. - This results in the eTLD+1 of "tést[.]blogspot[.]com" being computed as "tést[.]blogspot[.]com" instead of just "blogspot[.]com". - Since the eTLD+1 contains IDN, we perform the top domain skeleton check. - This check compares "tést[.]blogspot[.]com" against top domains and finds "blogspot[.]com" as a match. - This in turn records metrics and shows the UI. This CL excludes private registries in eTLD+1 computation. As a result, eTLD+1 of private registries will exclude the subdomain, e.g. eTLD+1 of "tést[.]blogspot[.]com" will now be computed as "blogspot[.]com". Since the new eTLD+1 does not have IDN, it will not trigger any further checks and the navigation will not be treated as a lookalike. Bug: 843361 Change-Id: Iaec1a0af61fa7aa9a2091bff3212171ba36034ad Reviewed-on: https://chromium-review.googlesource.com/c/1387670Reviewed-by:Tommy Li <tommycli@chromium.org> Commit-Queue: Mustafa Emre Acer <meacer@chromium.org> Cr-Commit-Position: refs/heads/master@{#618367}
Showing
Please register or sign in to comment