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 reaperhulk
Recipients barry, christian.heimes, jesstess, macfreek, r.david.murray, reaperhulk, sdaoden, torsten.becker, zvyn
Date 2017-06-02.16:08:26
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1496419707.28.0.968814895148.issue11783@psf.upfronthosting.co.za>
In-reply-to
Content
As someone who built an idna aware API for pyca/cryptography and deeply regrets it I'd like to weigh in on the side of saying that IDNA is a presentation issue and that supporting it in lower level APIs is the cause of many bugs, some of which can potentially be security issues. Users wanting to make requests to IDNA domains should be responsible for the encoding themselves so that impedance mismatches in encoding version are both discoverable and correctable.
History
Date User Action Args
2017-06-02 16:08:27reaperhulksetrecipients: + reaperhulk, barry, macfreek, christian.heimes, r.david.murray, jesstess, sdaoden, torsten.becker, zvyn
2017-06-02 16:08:27reaperhulksetmessageid: <1496419707.28.0.968814895148.issue11783@psf.upfronthosting.co.za>
2017-06-02 16:08:27reaperhulklinkissue11783 messages
2017-06-02 16:08:26reaperhulkcreate