: mailto:mclaas...@ocie.net
Voice: (574)232-3784
Fax: (574)232-4014
-Original Message-
From: e...@zusammenkunft.net [mailto:e...@zusammenkunft.net]
Sent: Wednesday, May 18, 2016 3:09 PM
To: HttpClient User Discussion
Subject: Re: Host name resolution
There are lots of reasons, and unfortunatelly
: "Mark A. Claassen"
To: HttpClient User Discussion
Sent: Mi., 18 Mai 2016 16:47
Subject: Host name resolution
Every once in a while, it seems that my apache HTTP client seems to resolve a
host name different that when I use the command line. We had done some
infrastructure work (month
Every once in a while, it seems that my apache HTTP client seems to resolve a
host name different that when I use the command line. We had done some
infrastructure work (months ago) and some of our internal domain names had
changed. Now, everything will work fine, until all of a sudden it will
gt; implementation to the socket factory. It looks like in HC 4.1, this is
>> deprecated. What is the preferred way of customizing host name resolution?
>>
>> I took a look at the source code, and I am guessing I will need to override
>> DefaultClientConnectionOpera
What is the preferred way of customizing host name resolution?
>
> I took a look at the source code, and I am guessing I will need to override
> DefaultClientConnectionOperator.resolveHostName(). But I want to be sure
> this is the best way.
For HC 4.1 I would say the same, this loo
Hi everyone. In HC 4.0, the way that a host name is converted to an
InetAddress object could be overridden by passing a custom HostNameResolver
implementation to the socket factory. It looks like in HC 4.1, this is
deprecated. What is the preferred way of customizing host name resolution?
I
