3 ms·
> DNS domain names, URLs, and email addresses can – and do – contain >0xff input Is that true? My understanding is that DNS never supported non-ASCII and so pu
by secondcoming 4y ago
> DNS domain names, URLs, and email addresses can – and do – contain >0xff input
Is that true? My understanding is that DNS never supported non-ASCII and so punycode was invented.
- wink 4y agoI mean, in the most basic sense you could always have non-ASCII chars in your filenames on a webserver, which could be part of a URL then.
- Beltalowda 4y agoDNS-the-protocol still doesn't support non-ASCII input, but DNS-as-people-use-it does. I expanded on that in another comment I just posted, so I won't repeat it here: https://news.ycombinator.com/item?id=34230218 https://news.ycombinator.com/item?id=34230218
- ElectricalUnion 4y agoBut is also very rare that you ask directly for domain name resolution in the first place; you are usually instead using something directly or indirectly that happens to be remote, and that eventually happens to have a punycode encoded non-ascii hostname or top level domain. But there's no garantee that you (or the libraries, or the libraries that your libraries use...) are only handling the ascii punycode. I can count on my fingers the number of places I invoked manual DNS lookups inside production code.