Have you tried it? The libraries you mention are bundled by requests (this is how the project handles it upstream) and it should work fine. I know it works for me...


Try this:

import requests
print(requests.get("https://sni.velox.ch/").text)


This should be present in the response:

<p><strong>Great! Your client </strong>[python-requests/1.2.3 CPython/3.3.2 Linux/3.9.5-1-ARCH] <strong>
sent the following TLS server name indication extension
(<a href="http://www.rfc-editor.org/rfc/rfc6066.txt">RFC 6066</a>)
in its ClientHello </strong>(negotiated protocol: TLSv1.2, cipher suite: ECDHE-RSA-AES256-GCM-SHA384)<strong>:</strong></p>
<pre> <strong>sni.velox.ch</strong></pre>
<p>In your request, this header was included:</p>
<pre> Host: sni.velox.ch</pre>

Yes, I've tried it, and it didn't work without those dependencies.
requests bundles urllib3, but without python2-ndg-httpsclientpy, urllib3 does not support SNI.
(See here: https://github.com/kennethreitz/requests/issues/749 for details).

Please note that this applies only to python2. Maybe you tested it with python > 3.2?

python2-pyasn1 is also required

It is a dependency of python2-ndg-httpsclient so it is not needed to be explicited in python2-requests

Didn't see this.

ndg-httpsclient also works without pyasn1.

It works without pyasn1 but it is required for subjectAltName support.

I may change it to an optdepend in ndg-httpsclient but for simplicity's sake I would rather leave it like this.

The whole point of ndg-httpsclient is to provide a more feature complete support for https than the one available in the standard library of python2, it makes not much sense imho to have it installed with only a subset of its functionalities.

Yes, it doesn't really matter. Sorry for the noise.

Thanks for the feedback