Re: [whatwg/url] Should we forbid U+226E (≮) and U+226F (≯) in hosts? (Issue #733)

Fundamentally, I'm not even sure why the decomposition of these characters is even relevant - UTS46 normalises them to a _composed_ form and Punycodes that, so none of these characters should ever result in naked ASCII `=`/`<`/`>` characters being sent over the wire -- and I think that's all that standards such as STD3, or DNS servers, routers, etc should care about; that it doesn't collide with other delimiters and whatnot.

So I see no technical reason why these characters should be disallowed. And I see no non-technical reason why we should disallow characters such as `≯`, while allowing all of the following:

`http://┴/` - box drawing character. Allowed => `http://xn--qxh/`

`http://∫/` - integral symbol. Allowed => `http://xn--jbh/`

`http://𝜢𝜠𝜰/` - Mathematical bold italic capitals. Allowed => `http://xn--qxad7b/`

`http://𐦖.𓀡.𓀈/` - Ancient Egyptian hieroglyphics. Allowed => `http://xn--6n9c.xn--3p7d.xn--ep7d/`

`http://helpme𓏎/` - Another hieroglyphic. U+133CE POT WITH LEGS. Allowed => `http://xn--helpme-gt36b/`


-- 
Reply to this email directly or view it on GitHub:
https://github.com/whatwg/url/issues/733#issuecomment-1381842351

You are receiving this because you are subscribed to this thread.

Message ID: <whatwg/url/issues/733/1381842351@github.com>