Hi Oleg,

No, I had not updated my code.
I updated my code as you said and it worked OK.
Thanks Oleg,

Nicolas de Pomereu

-----Original Message-----
From: Oleg Kalnichevski <[email protected]>
Sent: Tuesday, December 10, 2019 11:16 AM
To: HttpClient User Discussion <[email protected]>
Subject: Re: SSL failure when using new Async APIs in 5.0-beta6

On Tue, 2019-12-10 at 11:06 +0100, Nicolas de Pomereu wrote:
> Hi,
> I still have the problem with the new master version.
> (
> https://github.com/apache/httpcomponents-client/commit/f3c418c50a6ebba
> 4f7f89d568a542c5599956310
> )
> Enclosed  class call fails with javax.net.ssl.SSLHandshakeException:
> General SSLEngine problem
> (USE_WEBSITE_WITH_IP_DIFFERENT_THAN_INNET_ADDRESS  = true) Regards,
> Nicolas de Pomereu
>

You have not updated your code to use the #execute method with an explicit
HttpHost parameter, have you?

Oleg


> <<...>> <<...>>
> -----Original Message-----
> From: Oleg Kalnichevski <[email protected]>
> Sent: Thursday, December 5, 2019 4:56 PM
> To: HttpClient User Discussion <[email protected]>
> Subject: Re: SSL failure when using new Async APIs in 5.0-beta6 On
> Wed, 2019-12-04 at 15:07 +0100, Oleg Kalnichevski wrote:
> >
> > > On Tue, 2019-12-03 at 15:35 +0100, Nicolas de Pomereu wrote:
> > > > Hi,
> > > >
> > > > With HttpClient 5.0-beta6  Classic APIs, HttpClient call will
> work
> > > > using HttpHost with following code, even if initHost IP is
> > > > different from
> > > > destServerNameIP:
> > > >
> > > >   initHost = "www.acme.com";
> > > >   destServerNameIP = "100.100.100.100";
> > > >   destScheme = "https";
> > > >   port = 443;
> > > >
> > > >   InetAddress inetAddress =
> > > > InetAddress.getByName(destServerNameIP);
> > > >   final HttpHost target = new HttpHost(destScheme, inetAddress,
> > > > initHost, port);
> > > >
> > > > With HttpClient 5.0-beta6  new Async APIs for HTTP/2,
> HttpClient
> > > > will fail with a SSLEngineException failure if initHost IP is
> > > > different from destServerNameIP.
> > > >
> > > > Is this a new feature or a bug please?
> > > >
> >
> > I found out that async versions of HttpClient presently do not take
> > InetAddress parameter of HttpHost into account.
> >
> > Feel free to raise a JIRA if you want to track resolution of this
> > defect.
> >
> > I am seriously considering removing InetAddress attribute from
> > HttpHost. It should have never been added to the class in the first
> > place. Though I will see if there is an alternative fix that does
> not
> > involve any changes to the HttpHost as the first step.
> >
> > Oleg
> >
> The problem fixed in master with
>
https://github.com/apache/httpcomponents-client/commit/f3c418c50a6ebba4f7f89d568a542c5599956310
> Oleg
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [email protected]
> For additional commands, e-mail: [email protected]
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [email protected]
> For additional commands, e-mail: [email protected]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to