Re: [whatwg/url] Forbid < and > in hosts (#458)

I'm not opposed to forbidding ^ given that Chrome and Firefox already do.  I'd like to avoid having different character sets for special and non-special schemes until we find evidence that that is needed to mitigate significant compatibility issues, so let's just give it a try and I'll let you know if we find any problems in our third party apps or websites.
With all the characters *<>^|"^ we should definitely either fail to parse or succeed.  Percent encoding should not be done in URLs like http://*/ or http://</ and we should add web platform tests to verify behavior alignment.

-- 
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/458#issuecomment-565529658