New issue
Advanced search Search tips

Issue 718258 link

Starred by 0 users

Issue metadata

Status: Fixed
Owner:
Closed: May 2017
Components:
EstimatedDays: ----
NextAction: ----
OS: All
Pri: 3
Type: Feature



Sign in to add a comment

nassh: add IDNA support

Project Member Reported by vapier@chromium.org, May 4 2017

Issue description

today if you try to use an IDN, it fails.  we end up just trying to connect to a hostname using the encoded bytes.

for example, 日本.com will try \346\227\245\346\234\254.com when it should have used punycode to connect to xn--wgv71a.example.com.

seems like we should be able to import this guy:
https://github.com/bestiejs/punycode.js

license is MIT
 

Comment 2 by vapier@chromium.org, May 10 2017

Owner: vapier@chromium.org
Status: Fixed (was: Available)
forgot to link to this bug in the last CL:
  https://chromium-review.googlesource.com/495354

this will be part of 0.8.36.4+

Sign in to add a comment