all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Robert Pluim <rpluim@gmail.com>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: 26634@debbugs.gnu.org
Subject: bug#26634: 26.0.50; The network security manager doesn't understand IDNA domains
Date: Fri, 13 Apr 2018 17:38:10 +0200	[thread overview]
Message-ID: <87y3hrjevx.fsf@gmail.com> (raw)
In-Reply-To: <87lgdrw2ug.fsf@mouse.gnus.org> (Lars Ingebrigtsen's message of "Fri, 13 Apr 2018 17:19:51 +0200")

Lars Ingebrigtsen <larsi@gnus.org> writes:

> Robert Pluim <rpluim@gmail.com> writes:
>> Did you mean <https://appӏe.com> ?
>
> No, I meant https://аррӏе.com which is a totally different domain.  :-)
>
> Hm...  Oh, that's the 100% cyrillic one.  :-)  This is so confusing.
>

Fun, isnʼt it? Can we go back to 7-bit ASCII please?

> So eww definitely does the right thing with the mixed-script аррӏе.com,
> and I guess there's nothing to be done with the 100%-cyrillic case...
>
>> (FWIW, chrome is supposed to detect the 100% cyrillic case, but
>> doesnʼt as far as I can tell)
>
> What does Chrome do with that URL?
>
> Oh, I've got Chromium here, so I can just test...
>
> It displays https://xn--80ak6aa92e.com/ in the address bar.  Which
> is...  I guess...  a choice.

I donʼt mind that. Itʼs better than displaying the homograph.

Robert





  reply	other threads:[~2018-04-13 15:38 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-04-24  3:13 bug#26634: 26.0.50; The network security manager doesn't understand IDNA domains Lars Ingebrigtsen
2018-04-13 13:18 ` Lars Ingebrigtsen
2018-04-13 14:44   ` Lars Ingebrigtsen
2018-04-13 15:03     ` Robert Pluim
2018-04-13 15:19       ` Lars Ingebrigtsen
2018-04-13 15:38         ` Robert Pluim [this message]
2018-04-15 13:58           ` Lars Ingebrigtsen
2018-07-22 11:35 ` bug#26634: [Lars Ingebrigtsen] " Lars Ingebrigtsen

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=87y3hrjevx.fsf@gmail.com \
    --to=rpluim@gmail.com \
    --cc=26634@debbugs.gnu.org \
    --cc=larsi@gnus.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.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.