Skip to content
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

Fixes issue #3863 #4229

Merged
merged 3 commits into from
Aug 9, 2017
Merged

Fixes issue #3863 #4229

merged 3 commits into from
Aug 9, 2017

Conversation

NikosVlagoidis
Copy link
Contributor

Update the docs for issue #3863 .

@NikosVlagoidis
Copy link
Contributor Author

How tests are failing for Python 3.3. I have only changed one .rst on the docs

Copy link
Member

@Lukasa Lukasa left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I don't think the test failures will be relevant.

@@ -593,6 +593,10 @@ as using a HTTP one::
'https': 'socks5://user:pass@host:port'
}

Using socks5 proxy resolve domains through the client instead of the proxy server. This is done to be
in line with curl, which uses different schemes to decide whether to resolve via the proxy or via the client.
You need to use the scheme socks5h is you want to resolve domains through the proxy server.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Let's change this to:

Using the scheme socks5 causes the DNS resolution to happen on the client, rather than on the proxy server. This is in line with curl, which uses the scheme to decide whether to do the DNS resolution on the client or proxy. If you want to resolve the domains on the proxy server, use socks5h as the scheme.

@NikosVlagoidis
Copy link
Contributor Author

I update the docs accordingly.

@@ -593,6 +593,8 @@ as using a HTTP one::
'https': 'socks5://user:pass@host:port'
}

Using the scheme socks5 causes the DNS resolution to happen on the client, rather than on the proxy server. This is in line with curl, which uses the scheme to decide whether to do the DNS resolution on the client or proxy. If you want to resolve the domains on the proxy server, use socks5h as the scheme.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Can we surround socks and socks5 with double-backticks? That is, make it:

``socks``

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Do you mean socks5 and socks5h right?

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I do. ;)

Copy link
Member

@Lukasa Lukasa left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Perfect, thankyou so much!

@Lukasa Lukasa merged commit f78a579 into psf:master Aug 9, 2017
@github-actions GitHub Actions bot locked as resolved and limited conversation to collaborators Sep 4, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants