It’s absolutely valid and thank you for it. I have closed it because I added it to the “future features” section on the Web page and I don’t want to have hundreds of requests pending forever.
Feature Req: Socks5 Proxy Support
- optionally use user-supplied proxy settings on a per-account basis
- allow for dns resolution via the proxy (e.g. for use with Orbot)
HttpClient should already support SOCKS proxies, so it should be enough to set
socksProxyPortin the system environment (or locally) like here: http://stackoverflow.com/a/3078299
Do you know if there’s a way to set these variables globally? How is your current setup, which SOCKS proxy do you use and how do other applications handle this?
Any news on this? Otherwise, I’ll close this issue.
Closing because of missing user response.
Hello, I bring this up cause I think it would be a nice feature to have full SOCKS and TOR support for each user since OkHttp supports it. Although I have to admit that adding such a feature may won’t affect much non advanced users.
@rfc2822 I don’t think it there is a mechanism to set these variables globally and force an application to use it except for using a VPN which is a totally different thing.
For the time I fixed it just by adding this line
.proxy(Proxy(Proxy.Type.SOCKS, InetSocketAddress("127.0.0.1", 9050)))
to the OkHttpClient.Builder but this solution affects all the users and it only works if you provide the base URL (TOR doesn’t support UDP yet).