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 mnot
Recipients Dima.Tisnek, Dolf.Andringa, exarkun, giampaolo.rodola, grooverdan, janssen, jcea, markk, mnot, pdp, pitrou, scott.tsai
Date 2014-01-08.03:49:15
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
This is *not* a feature request, it's a bug fix in the underlying protocols. 

Client sides that do not send SNI are actively hurting the Web and the Internet by constraining the deployment of TLS. 

The closest analogy would be if Python's HTTP client side didn't emit a Host header, and the excuse were "But we only advertise ourselves as HTTP/1.0." The biggest difference being that this has additional security impact.

The pain of lack of support for SNI is completely borne by the server-side, not the client (here, Python). As such, this is not a feature for Python client-side developers, but an interop / scaling / security issue for the Web and Internet overall.
Date User Action Args
2014-01-08 03:49:16mnotsetrecipients: + mnot, jcea, exarkun, janssen, pitrou, giampaolo.rodola, scott.tsai, pdp, grooverdan, Dolf.Andringa, Dima.Tisnek, markk
2014-01-08 03:49:16mnotsetmessageid: <>
2014-01-08 03:49:16mnotlinkissue5639 messages
2014-01-08 03:49:15mnotcreate