-
Notifications
You must be signed in to change notification settings - Fork 1.6k
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
Problem with DNS name resolution via socks (Tor) proxy #1682
Comments
BTW, this is an example of it working just fine with HttpURLConnection
|
@fancellu Your HttpURLConnection based sample doesn't work for me. And as far as I know, Java doesn't support this, see https://bugs.openjdk.java.net/browse/JDK-8028776. |
Mmm, actually, I see the DNS resolution in Charles, not in AHC, so I guess it works now and the Java issue should be closed. |
Charles? It very much does work for me:
BTW, I love Gatling, |
I got this working for Gatling (DNS resolution was already working fine for HTTP proxies), see gatling/gatling#3835. Now, regarding AHC, honestly, the code base is very different now and I don't now if/when I'll have time for this someday. The best solution would be to contribute a fix. |
My work around is to use okhttp https://gist.github.com/fancellu/df6dde59249edf8401b28bbc44a78cbc |
@TomGranot I'm also noticing this for other Socks 5 proxy traffic |
Run up a socks proxy, for example Tor browser proxy on port 9150
Run this code
I get
If I point it at
https://check.torproject.org/
it works fineDo I have to do something else to make it not fail?
Thanks
The text was updated successfully, but these errors were encountered: