➜

This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author christian.heimes
Recipients barry, christian.heimes, jesstess, macfreek, r.david.murray, sdaoden, torsten.becker, zvyn
Date 2017-06-02.15:55:39
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1496418939.22.0.647310540785.issue11783@psf.upfronthosting.co.za>
In-reply-to
Content 
Adding automatic IDNA decoding is like opening Pandora's box.

uts46 is not necessarily the correct solution. The correct handling of internationalized domain names depends on multiple factors: TLD, remote application and more. You actually have to know if the remote peer uses 2003 or 2008. For any user facing application you cannot simply expose all of IDNA to the user (homoglypic confusion attacks).
History
Date User Action Args
2017-06-02 15:55:39christian.heimessetrecipients: + christian.heimes, barry, macfreek, r.david.murray, jesstess, sdaoden, torsten.becker, zvyn
2017-06-02 15:55:39christian.heimessetmessageid: <1496418939.22.0.647310540785.issue11783@psf.upfronthosting.co.za>
2017-06-02 15:55:39christian.heimeslinkissue11783 messages
2017-06-02 15:55:39christian.heimescreate