The DNS resolver is part of the problem creating a custom DnsResolver does
not appear to resolve the issue.
If the address is https://facebookcorewwwi.onion/ the server tries to
resolve this and fails, no ip address exists. This results in an
UnknownHostException which is the correct behavior if
On Mon, 2015-03-30 at 15:18 -0600, Lucas Sapp wrote:
Hello Everyone,
I have discovered an issue when I try to reach addresses that do not
resolve an IP address but are still valid and can be accessed with a
SOCKS/HTTP Proxy. I am using HttpClient 4.3.4. The error seems to occur
when it
Hello Everyone,
I have discovered an issue when I try to reach addresses that do not
resolve an IP address but are still valid and can be accessed with a
SOCKS/HTTP Proxy. I am using HttpClient 4.3.4. The error seems to occur
when it tries to resolve the address prior to connecting the socket. It
