-
Notifications
You must be signed in to change notification settings - Fork 10.2k
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
Add --socks-proxy parameter to use socks proxy #6353
Conversation
This allows the user to specify a socks proxy to tunnel the connection through.
This approach forces all network traffic going through the SOCKS proxy. The urllib2 handler approach might be better. |
Why is it a bad thing if all traffic goes through the proxy? Which traffic do you want bypassing the proxy? |
I think I nearly got it. Will update this PR tomorrow. |
As already mentioned in IRC conversation you should ensure there are no problems bundling SocksiPy with py2exe in the first place. |
Closes #6370.
That's how YouTube reports them in their DASH manifest.
This allows the user to specify a socks proxy to tunnel the connection through. This feature requires that PySocks is available. If the user tries to use a SOCKS proxy without PySocks available an error is printed and the process is aborted.
This allows the user to specify a socks proxy to tunnel the connection through. This feature requires that PySocks is available. If the user tries to use a SOCKS proxy without PySocks available an error is printed and the process is aborted.
Sorry about all the commits. I'm going to close this one and create a new clean PR. |
resolves #402
This allows the user to specify a socks proxy to
tunnel the connection through.
This does add a soft dependency on socksipy. Normal operation will work without it,
but socks support obviously depends on it.
I did some positive tests and a videos were downloaded from youtube via the socks proxy.
I did not test other hosts, but assume it should work the same.
I am not certain what happens if --socks-proxy and --proxy are specified simultaneously. Did not have a http proxy to test this.
The unittests have not finished running yet, but since none of my code (except adding the option) is actually run if the --socks-proxy option is not set it seems highly unlikely for it break existing functionality.