session.http: re-use SSLContext in ProxyManager #6025
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
See #6018 (comment)
This uses a reference of the same
SSLContextobject in theurllib3.ProxyManager's connection pool keywords as the regularurllib3.PoolManager.I can't verify the proxy issue on kick.com though, as kick is blocking my entire server network. I'm using a socks5 tunnel via OpenSSH on my server, and regular HTTPS requests from the server don't work either.
Re-using the same SSLContext however is the correct thing to do:
Example from related projects: