You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In the 2nd example, the domain has a trailing dot. This is valid, as it indicates this is unambiguous FQDN. I was passing output from DNS records into EffectiveTLDPlusOne when I noticed this issue.
I suggest the EffectiveTLDPlusOne ignores the trailing dot if one exists.
$ go version
go version go1.4.2 darwin/amd64
The text was updated successfully, but these errors were encountered:
ianlancetaylor
changed the title
publicsuffix.EffectiveTLDPlusOne() parses domains incorrectly if there is a trailing dot
x/net/publicsuffix: EffectiveTLDPlusOne() parses domains incorrectly if there is a trailing dot
Jul 12, 2015
Thanks @crawshaw and @nigeltao. Sorry I didn't find the previous bug, feel free to close this as a DUP of #7125. I will strip the trailing dot myself. I had already been lowercasing the domain, but not doing a great job of canonicalising the domain otherwise.
prints
In the 2nd example, the domain has a trailing dot. This is valid, as it indicates this is unambiguous FQDN. I was passing output from DNS records into EffectiveTLDPlusOne when I noticed this issue.
I suggest the EffectiveTLDPlusOne ignores the trailing dot if one exists.
The text was updated successfully, but these errors were encountered: