Re: [whatwg/url] Forbidden host code points should include all C0 controls & U+007F (#627)

Ok, but I woudn't say this is off topic, the definition is used in the opaque-host-parser. 

There have been other, more recent additions to the forbidden-host-codepoints over time, such as `<`, `|`, `>`, and `^` that have also affected opaque-hosts and caused more of them to fail. 

> It should be a concern, because it would make them even less backwards compatible.

In that case, how about percent-encoding the forbidden-host-codepoints (minus `%`) in opaque hosts rather than failing on them? Then Chrome and Firefox would agree with the standard at least on the href of the affected URLs.

Otherwise, the forbidden-host-codepoints can be replaced with separate forbidden-domain-codepoint and forbidden-opaque-host-codepoint sets.




-- 
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/627#issuecomment-971331375