-
Notifications
You must be signed in to change notification settings - Fork 75
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
Supported socks5 proxy for crypto-ws-client #18
Conversation
use fast_socks5 crate to wrap the TcpStream so that we can use socks5 proxy, please set SOCKS_PROXY env before run executable
use fast_socks5 crate to wrap the TcpStream so that we can use socks5 proxy, please set https_proxy env before run executable. eg. https_proxy=socks5://127.0.0.1:10808
[skip ci]
Hi @GhostLee , thank your for this great job. One quick question, have you run this against a real socks5 proxy? Is your code working? |
Related to snapview/tungstenite-rs#177 |
yes, I use it in my project. |
[skip ci]
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Great job!
I published new versions of |
* feat: support socks5 proxy for websocket client use fast_socks5 crate to wrap the TcpStream so that we can use socks5 proxy, please set SOCKS_PROXY env before run executable * feat: support socks5 proxy with https_proxy env for websocket client use fast_socks5 crate to wrap the TcpStream so that we can use socks5 proxy, please set https_proxy env before run executable. eg. https_proxy=socks5://127.0.0.1:10808 * refactor: remove tests [skip ci] * fix: support http_proxy [skip ci] Co-authored-by: GhostLee <[email protected]>
Use
fast_socks5
crate to wrap the TcpStream so that we can use socks5 proxy, please set https_proxy env before run executable.eg.
https_proxy=socks5://127.0.0.1:10808