-
Notifications
You must be signed in to change notification settings - Fork 33
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Incompatibility with requests 2.32.3 - custom SSLContext via a Transport Adapter #55
Comments
This issue is now being hopefully fixed in psf/requests#6731 A very quick fix would be to follow mikf/gallery-dl@6cfbc10 suit and place this within |
Ok |
@vog Sorry, but this problem is still current with Could you reopen it? |
Hi, |
Ok, reopened. Pull requests are welcome. |
@vog I'll be happy to provide a one-line pull request to fix the issue. But I was wondering if you'd prefer putting in a workaround (which will be superfluous once 2.32.4 is released/the above linked PR is merged) or just wait for said PR to land in requests.... |
Never mind, we quickly added the fix of on our own, and released requests_pkcs12 version 1.25: Our local test suite runs fine with it. Please check whether this solves the issue for you as well. |
Works for me, was exactly what I was experimenting with, too :) |
Thanks for your quick feedback. 👍 |
Leaving this issue open as a reminder to revert that workaround as soon as
|
This might be a false positive - but from preliminary experimentation, it seems like a recent change in requests might cause issues with requests_pkcs12.
With requests 2.32.0, a breaking change was introduced that returned every call with that involved requests_pkcs12 with
SSLContext via a Transport Adapter
.requests 2.32.3 (still unreleased as of right now, apparently scheduled for Tuesday) aims to fix this issue (Allow for overriding of specific pool key params #6716), but now all calls involving requests_pkcs12 fail with
SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed: unable to get local issuer certificate
for me.I'll try to dig a little deeper and see if this is indeed something that requires changes here - I just wanted to provide a heads-up in case 2.32.3 is indeed shipping a breaking change.
Minimal example:
The text was updated successfully, but these errors were encountered: