Skip to content

Conversation

delfick
Copy link
Contributor

@delfick delfick commented Nov 8, 2015

If you have assert_hostname turned off and are using a proxy on your
computer then assert_hostname wasn't being properly set on the pool
connection and it was failing to connect to docker

If you have assert_hostname turned off and are using a proxy on your
computer then assert_hostname wasn't being properly set on the pool
connection and it was failing to connect to docker

Signed-off-by: Stephen Moore <stephen@delfick.com>
@delfick
Copy link
Contributor Author

delfick commented Nov 8, 2015

https://github.com/kennethreitz/requests/blob/master/requests/adapters.py#L253 is the block that uses something other than self.poolmanager to create the connection

@shin-
Copy link
Contributor

shin- commented Nov 9, 2015

LGTM 👍

@dnephin
Copy link
Contributor

dnephin commented Nov 9, 2015

Code change looks ok to me.

Do you think this is a bug in requests ? I'm not sure I understand why we have to handle this

@delfick
Copy link
Contributor Author

delfick commented Nov 10, 2015

I agree that it would be nice if requests actually passed assert_hostname around.

I'm not sure how that change would look though.

@shin- shin- added this to the 1.6.0 milestone Nov 24, 2015
shin- added a commit that referenced this pull request Nov 24, 2015
Ensure assert_hostname is set on the pool connection
@shin- shin- merged commit 43b0ea5 into docker:master Nov 24, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants