Skip to content

Conversation

@RobertFischer
Copy link
Contributor

I didn't see exactly how to test the usage of a SOCKS5 proxy via the environment variable -- everything that I saw said that it just should work. If you point me in the direction of how to write a test, I'm happy to do so.

@snoyberg
Copy link
Owner

I don't understand the comment, can you clarify what you mean?

@RobertFischer
Copy link
Contributor Author

From what I'm understanding, the change that I made will accept "socks5://" and "socks5h://" as the prefix to the HTTPS_PROXY and HTTP_PROXY strings. But I didn't see how to write a test to prove that using those URL prefixes would actually connect us to a SOCKS5 proxy and successfully interact with it.

@snoyberg
Copy link
Owner

It looks fine to me. Ideally we would have some kind of a docker-compose based test that actually sets up proxy servers, but that doesn't exist right now.

@snoyberg snoyberg merged commit 89d5e6b into snoyberg:master Feb 15, 2017
@RobertFischer RobertFischer deleted the RobertFischer/socks5 branch February 20, 2017 00:03
snoyberg added a commit that referenced this pull request Feb 20, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants