From: Name Surname <augeus@outlook.com>
To: "libc-help@sourceware.org" <libc-help@sourceware.org>
Subject: Re: getaddrinfo chokes at hostnames containing "emoji" characters
Date: Wed, 16 May 2018 14:04:00 -0000 [thread overview]
Message-ID: <VI1PR09MB0685507AEDB1AD3EB926BD63CC920@VI1PR09MB0685.eurprd09.prod.outlook.com> (raw)
In-Reply-To: <50fefc33-ca42-37ff-4b7d-162e1d6b81eb@redhat.com>
Florian Weimer wrote:
> On 05/16/2018 10:40 AM, Name Surname wrote:
>> Greetings everyone.
>>
>> I recently bought a domain name containing "emoji" characters, as a
>> novelty and in order to do some experiments. I tried getting the IP
>> address associated to it using getaddrinfo, however, it errs and returns
>> "Name or service not known". The same thing happens with any program
>> that uses glibc for name resolution. I understand that emoji domains are
>> not valid according to IDNA2008, however, some ccTLDs sell them, they
>> were supported according to IDNA2003, and web browsers resolve them
>> normally according to IDNA2003 (at least firefox does).
>>
>> Is this a bug or a feature?
>
> In the near future, glibc will use the system libidn2 library to
> implement AI_IDN getaddrinfo support. You will have to convince the
> libidn2 maintainers to enable Emoji support (by default), but as long as
> there is no published standard for that at all (perhaps with the
> exception of Unicode TR46 transitional mode, which is not recommended),
> this seems difficult.
>
> Thanks,
> Florian
>
> .
>
It seems that, according to the WHATWG URL standard, IDNs should be
processed as per IDNA2008:
> Let result be the result of running Unicode ToASCII with
> domain_name set to domain, UseSTD3ASCIIRules set to beStrict,
> CheckHyphens set to false,
> CheckBidi set to true, CheckJoiners set to true,
> *processing_option set to Nontransitional_Processing*,
> and VerifyDnsLength set to beStrict.
Source: https://url.spec.whatwg.org/#idna
(Emphasis mine)
If I am understanding the standard correctly, then discussion of this
matter is moot, as this implies that emoji domains are not even
considered valid URLs.
next prev parent reply other threads:[~2018-05-16 14:04 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-16 8:40 Name Surname
2018-05-16 9:10 ` Florian Weimer
2018-05-16 9:49 ` Name Surname
2018-05-16 14:04 ` Name Surname [this message]
2018-05-16 14:09 ` Florian Weimer
2018-05-16 18:20 ` Name Surname
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=VI1PR09MB0685507AEDB1AD3EB926BD63CC920@VI1PR09MB0685.eurprd09.prod.outlook.com \
--to=augeus@outlook.com \
--cc=libc-help@sourceware.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).