-
Notifications
You must be signed in to change notification settings - Fork 133
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
Http proxy support #276
Merged
Merged
Http proxy support #276
Changes from all commits
Commits
Show all changes
5 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is there a reason to pass these values directly in the
kw
of the.get
and.post
calls?Checking the requests documentation it looks like just setting the
proxies
kw, as you did below, should be enough.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Would you recommend to pass the
proxies
dict as a keyword to thetransport.post
andtransport.get
methods? Would be fine with me but i thought thetransport
module is meant to be an abstraction for the synchronous HTTP requests API. If so it should better not userequests
specific constructs. Should I refactor the PR to pass theproxies
dict directly totransport
?There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Oh no. I just mean, you already provide the
proxies
keyword inside of the transport calls. Is there a need to also specify the proxy settings at each call site to the transport? I'm curious why we also passproxy
proxy_user
proxy_password
to thetransport.get
if the implementation oftransport.get
should be providing theproxies
keyword now.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The
_get_proxy_cfg
method in thetransport
module builds theproxies
config dict for requests. To do so it needs access to thehttp_proxy
,http_proxy_user
andhttp_proxy_password
settings. So either we access the settings in thetransport
module or we need to pass alonghttp_proxy
,http_proxy_user
andhttp_proxy_password
as keywords when we call atransport
method. Would you prefer another solution? The settings could be passed along as an argument as well, or stored intransport
as a thread local e.g.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ah hah. Now I get it. I apologize, I was focused on the kw being pass through to the actual session call, and missed that it is used, as you say, to build the
proxies
value from theSETTINGS
. This is an interesting scenario where, as you say, the SETTINGS object might preferably be refactored to be more shareable to all modules. But that isn't necessary for this change. Thank you for your patience answering my question and work on this PR, I'll get it merged.