-
-
Notifications
You must be signed in to change notification settings - Fork 267
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
Passing proxies to a websocket #415
Comments
I've had a dig around and got it to work, I'm not sure if it's a bug or not but someone might be able to figure that out, but using (was able to test as I have access to a few proxy providers and know of a websocket url that only works with some - using the first method made connections no matter the proxies whereas the second method failed on the proxies I expected to fail) |
Thanks for posting your findings back. I think we should add something like |
Ah right, makes more sense now, would it be nice to have a routine that converts the |
The question
I just wanted clarity on using proxies with a websocket specifically, I'm assuming that if I set up a session with certain proxies, then use the
ws_connect
method then the proxies will be utilised for that request? E.g.The text was updated successfully, but these errors were encountered: