[whatwg/url] Reject non-numeric hostnames that end in numbers. (#619)

This is aimed at addressing issue #560.  If the last component of a URL's hostname is numeric, it's parsed as an IPv4 hostname, and if that fails, the URL's host is rejected.  e.g., "foo.0", "bar.0.09", "a.1.2.0x.", "1.2.3.4.5" were all previously considered valid non-IPv4 hostnames, but are now all rejected.  See #560 for more discussion on why allowing these are potentially concerning.

- [ ] At least two implementers are interested (and none opposed):
   * Chrome
   * … (annevk expressed support in #560, but not sure that counts as strong enough support)
- [ ] [Tests](https://github.com/web-platform-tests/wpt) are written and can be reviewed and commented upon at:
   * …
- [ ] [Implementation bugs](https://github.com/whatwg/meta/blob/main/MAINTAINERS.md#handling-pull-requests) are filed:
   * Chrome: …
   * Firefox: …
   * Safari: …

(See [WHATWG Working Mode: Changes](https://whatwg.org/working-mode#changes) for more details.)

I will be putting together and uploading tentative tests later today/tomorrow.
You can view, comment on, or merge this pull request online at:

  https://github.com/whatwg/url/pull/619


-- Commit Summary --

  * Reject non-numeric hostnames that end in numbers.

-- File Changes --

    M url.bs (48)

-- Patch Links --

https://github.com/whatwg/url/pull/619.patch

https://github.com/whatwg/url/pull/619.diff


-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/whatwg/url/pull/619