-
-
Notifications
You must be signed in to change notification settings - Fork 95
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Punycode domains are not properly validated #239
Comments
Any help diagnosing where in whatwg-url (or perhaps https://github.com/jsdom/tr46/) this is breaking would be much appreciated. As usual, the goal is to match specs as 1:1 as possible so this kind of diagnostic would probably look like: "here is the spec, it says X. But your code is doing Y." |
I also noticed Edit: web-platform-tests/wpt#37993 now tracks this. Will likely not merge until the specification issue is done. |
The cases in the OP seem to get fixed by mathiasbynens/punycode.js#124 .
A few hundred other cases from web-platform-tests/wpt#38080 still fail. Will comment over there. |
The issue with Ideally, UTS 46 should clarify this point, excluding empty labels from Bidi Rule consideration. We should add this item to whatwg/url#744 if there's still time. |
That's the second comment there, right? Already submitted. |
Ah, right. |
Start with the input:
http://xn--ls8h/
It works, as it should, and the result is the same. It's the poop emoji, in case you were wondering. It's in the WPT tests.
Anyway, we can just start adding text to the end of this. For example:
All of these inputs are invalid. Safari refuses to parse them, and my own IDNA implementation agrees. The tail part of the Punycode domain (after the
xn--
) should only consist of ASCII alphanumerics; having"="
signs in there (in the input) is clearly invalid.The text was updated successfully, but these errors were encountered: