-
-
Notifications
You must be signed in to change notification settings - Fork 60
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
Upstream Proxy Server #58
Comments
hi @bacnt2412, thank you for sharing this use case. Is it that you would like to be able to associate a remote proxy to the simple socks server for upstream communication at the time you configure it? Any other context could be helpful too... not sure what to ask exactly, but trying to get a sense of how you envision or would like to work with simple-socks in this scenario. |
same https://www.npmjs.com/package/proxy-chain have option "upstreamProxyUrl". But proxy-chain don't support socks5 |
Same issue. Any updates? |
Same issue. Wants to support it. |
I’ve been reviewing the RFC and researching more about chaining proxy requests over socks. I think what might help you is something like the proxychains utility (https://github.com/rofl0r/proxychains-ng). To effectively specify an upstream server that is another proxy (and so on and on), the CONNECT portion of the exchange would need to contain the second proxy details, but there is no specification for supplying auth or even further downstream proxies (https://datatracker.ietf.org/doc/html/rfc1928#section-4). Would the proxychains utility help you in this scenario? |
I am interested in using your server in the folowing configuration. We currently have SOCKS5 proxies that do not support authentication. We'd like to have this setup:
CLIENT ---> SIMPLE-SOCKS ---> REMOTE_PROXY ---> WEB/WHATEVER
The text was updated successfully, but these errors were encountered: