URL parser inconsistency. #11707

Activity

1. mscdex

   added

   whatwg-urlIssues and PRs related to the WHATWG URL implementation.Issues and PRs related to the WHATWG URL implementation.

   on Mar 6, 2017
2. TimothyGu commented on Mar 6, 2017

   

   TimothyGu

   on Mar 6, 2017

   Last edited by TimothyGu

   Member

   More actions

   Thanks for reporting! This has been fixed in #11549, which enables stricter parsing of hostnames as specified by the WHATWG URL Standard. The patch should be released in the next v7.x.
3. TimothyGu

   closed this as completedon Mar 6, 2017
4. TimothyGu commented on Mar 6, 2017

   

   TimothyGu

   on Mar 6, 2017

   Member

   More actions

   One thing to note is that while most browsers seem to accept the URL, #11549 actually throws an error on such cases:

   > new url.URL('http://.test.com').hostname
   TypeError: Invalid URL
       at URL.onParseComplete (internal/url.js:87:11)
       at parse (internal/url.js:110:11)
       at new URL (internal/url.js:211:5)
       at repl:1:1
   

   That is, again, in compliance with the URL Standard.
5. DylanPiercey commented on Mar 10, 2017

   

   DylanPiercey

   on Mar 10, 2017

   Author

   More actions

   @TimothyGu thanks for that I had no idea.