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

> Why'd you folks do this without offering any means to disable it?
> 
> This breaks compatibility _irreparably_ for our software, see [a forum post](https://forum.cfx.re/t/nui-files-fail-to-load/4934989/10) in this regard.
> 
> I genuinely keep being amazed by how web browser vendors love to break compatibility at random. From the _issue_ you linked earlier, metrics from 'Chrome' don't contain use cases from downstream users of Chromium, nor do we have a way to report such metrics to 'Chrome' in the first place or manpower to track every single little change you people are making.

See issue #560, linked in the first post for more details.  The specs around the host parser, the public suffix list, and the definition of site, are not very compatible in this case.  This was a fix for potential security issues, due to https://foo.127.1 having an eTLD+1 of 127.1, and thus a schemeful site of https://127.1, which as a URL, maps to https://127.0.0.1/.

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

Message ID: <whatwg/url/pull/619/c1288187488@github.com>