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
hwo411
changed the title
canonicalize_url incorrectly handles port when using hostname that requires IDNA encoding
canonicalize_url incorrectly handles port and multiple dots in the end of the domain when using hostname that requires IDNA encoding
Mar 26, 2024
As you can see, single dot is handled properly, but with 2+ dots it doesn't encode the domain at all.
Update: it seems to be an invalid url according to the standard, so maybe the behavior is correct, though in other languages some url validators accept it and handle normally. So not sure if this addendum has to be fixed, I'll revert the title back.
hwo411
changed the title
canonicalize_url incorrectly handles port and multiple dots in the end of the domain when using hostname that requires IDNA encoding
canonicalize_url incorrectly handles port when using hostname that requires IDNA encoding
Mar 26, 2024
Hello,
We just recently encountered the following problem:
which returns
https://xn--e1aybc.xn--:33-qdd4dec/
while the expected value is
https://xn--e1aybc.xn--e1aybc:33/
And that happens to every hostname that required IDNA encoding for their TLD.
Could you please fix this behavior?
The text was updated successfully, but these errors were encountered: