Re: [whatwg/url] Large ports of non special urls (#257)

The compatibility issue was from only one company's web content ecosystem used by a few apps, but they're changing their content.  I think we should keep the port as conceptually limited to 16-bit integers and fail to parse any ports larger than 65535, regardless of scheme.  This way non-JavaScript URL implementations can do something reasonable with the port.  Mine returns std::optional<uint16_t>, but other languages have similar constructs.  So I think we should keep the spec as-is and add a test verifying that parsing asdf://host:65536/ fails.

-- 
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/issues/257#issuecomment-285553590