Announcing an HTTP-RPC project
Using this lib, v5 of course. Open source on github here: - http://java-http-rpc.mbake.org I had to add some libs to get mime to work. Happy to answer any questions. Vic - To unsubscribe, e-mail: httpclient-users-unsubscr...@hc.apache.org For additional commands, e-mail: httpclient-users-h...@hc.apache.org
RE: Issue sending https to an http endpoint
Hi,
Ok, I will have to wait for my docker expert to return from his holidays this
September. When he's back we will build the container.
Thanks,
Joan.
-Original Message-
From: Oleg Kalnichevski
Sent: Tuesday, August 27, 2019 11:30 AM
To: HttpClient User Discussion
Subject: Re: Issue sending https to an http endpoint
On Tue, 2019-08-27 at 11:27 +0200, Joan grupoventus wrote:
> Hi Oleg,
>
> I uploaded the httpcore-5b9 we generated to the git. Is it possible
> you download it and try just one test with async Http5 to check if it
> works for you?
> We have checked the jar and it seems to be correct, so if you are
> using the same version I don't understand why it works for you and not
> for us.
>
> Thanks,
> Joan.
>
Could you please try to reproduce the issue inside a docker container?
Oleg
> -Original Message-
> From: Oleg Kalnichevski
> Sent: Friday, August 23, 2019 5:32 PM
> To: HttpClient User Discussion
> Subject: Re: Issue sending https to an http endpoint
>
> On Fri, 2019-08-23 at 17:24 +0200, Joan grupoventus wrote:
> > Hi Oleg,
> >
> > Is this the right link to build the httpcore-b9?
> > https://github.com/apache/httpcomponents-core
> >
>
> Yes, it is.
>
> Oleg
>
> > We checked the version of our jar and it seems to be correctly. Is
> > there something else we have to build? We are already using the
> > latest httpclient (httpclient5-5.0-beta5)
> >
> > Thanks,
> > Joan.
> >
> > -Original Message-
> > From: Oleg Kalnichevski
> > Sent: Friday, August 23, 2019 9:49 AM
> > To: HttpClient User Discussion
> > Subject: Re: Issue sending https to an http endpoint
> >
> > On Thu, 2019-08-22 at 23:12 +0200, Joan grupoventus wrote:
> > > Hi Oleg,
> > >
> > > Well, not sure what's happening. In "our" git
> > > (https://github.com/joanbalaguero/HttpClient) I have uploaded 4
> > > files that connect by https to the problematic url.
> > >
> > > The "TestSync" is using a sync http5 client and works, ends with
> > > an exception "javax.net.ssl.SSLException: Unrecognized SSL
> > > message, plaintext connection?"
> > > The " TestAsync41ResponseConsumer.java" is using the async http
> > > 4.1.3
> > > client with an "HttpAsyncResponseConsumer" and works, ends with an
> > > exception
> > > "javax.net.ssl.SSLException: Unrecognized SSL message, plaintext
> > > connection?"
> > >
> > > The "TestAsync5FutureCallback" and "TestAsync5ResponseConsumer"
> > > are
> > > using an async http5 client (httpclient5-5-beta5 and
> > > httpcore5-5-beta9), the first one with a
> > > "FutureCallback" and the second with a
> > > "AsyncResponseConsumer". Both hang forever.
> > >
> > > So if this is not a bug in http5, what's wrong with these two last
> > > samples?
> > > The code there is minimal.
> > >
> >
> > Joan,
> >
> > I see nothing wrong with those samples and they all work for me
> > (HttpClient 5.0b5 + HttpCore 5.0b9-SNAPSHOT).
> >
> > Oleg
> > ---
> > 2019-08-23 09:46:30,669 DEBUG
> > [main][org.apache.hc.client5.http.impl.async.InternalHttpAsyncClien
> > t]
> > ex-0001: preparing request execution
> > 2019-08-23 09:46:30,676 DEBUG
> > [main][org.apache.hc.client5.http.protocol.RequestAddCookies]
> > CookieSpec selected: standard
> > 2019-08-23 09:46:30,680 DEBUG
> > [main][org.apache.hc.client5.http.protocol.RequestAuthCache] Auth
> > cache not set in the context
> > 2019-08-23 09:46:30,680 DEBUG
> > [main][org.apache.hc.client5.http.impl.async.AsyncProtocolExec] ex-
> > 0001: target auth state: UNCHALLENGED
> > 2019-08-23 09:46:30,681 DEBUG
> > [main][org.apache.hc.client5.http.impl.async.AsyncProtocolExec] ex-
> > 0001: proxy auth state: UNCHALLENGED
> > 2019-08-23 09:46:30,683 DEBUG
> > [main][org.apache.hc.client5.http.impl.async.AsyncConnectExec] ex-
> > 0001: acquiring connection with route {s}->
> > https://54.38.179.182:8083
> > 2019-08-23 09:46:30,684 DEBUG
> > [main][org.apache.hc.client5.http.impl.async.InternalHttpAsyncClien
> > t]
> > ex-0001: acquiring endpoint (3 MINUTES)
> > 2019-08-23 09:46:30,685 DEBUG
> > [main][org.apache.hc.client5.http.impl.nio.PoolingAsyncClientConnec
> > ti
> > onManager] ex-0001: endpoint lease request (3 MINUTES) [route:
> > {s}->https://54.38.179.182:8083][total kept alive: 0; route
> > allocated: 0 of 5; total allocated: 0 of 25]
> > 2019-08-23 09:46:30,689 DEBUG
> > [main][org.apache.hc.client5.http.impl.nio.PoolingAsyncClientConnec
> > ti
> > onManager] ex-0001: endpoint leased [route: {s}->
> > https://54.38.179.182:8083][total kept alive: 0; route allocated: 1
> > of 5; total allocated: 1 of 25]
> > 2019-08-23 09:46:30,690 DEBUG
> > [main][org.apache.hc.client5.http.impl.nio.PoolingAsyncClientConnec
> > ti
> > onManager] ex-0001: acquired ep-
> > 2019-08-23 09:46:30,690 DEBUG
> > [main][org.apache.hc.client5.http.impl.async.InternalHttpAsyncClien
> > t]
> > ex-0001: acquired endpoint ep-
> > 2019-08-23 09:46:30,691 DEBUG
> >
Re: Issue sending https to an http endpoint
On Tue, 2019-08-27 at 11:27 +0200, Joan grupoventus wrote:
> Hi Oleg,
>
> I uploaded the httpcore-5b9 we generated to the git. Is it possible
> you download it and try just one test with async Http5 to check if it
> works for you?
> We have checked the jar and it seems to be correct, so if you are
> using the same version I don't understand why it works for you and
> not for us.
>
> Thanks,
> Joan.
>
Could you please try to reproduce the issue inside a docker container?
Oleg
> -Original Message-
> From: Oleg Kalnichevski
> Sent: Friday, August 23, 2019 5:32 PM
> To: HttpClient User Discussion
> Subject: Re: Issue sending https to an http endpoint
>
> On Fri, 2019-08-23 at 17:24 +0200, Joan grupoventus wrote:
> > Hi Oleg,
> >
> > Is this the right link to build the httpcore-b9?
> > https://github.com/apache/httpcomponents-core
> >
>
> Yes, it is.
>
> Oleg
>
> > We checked the version of our jar and it seems to be correctly. Is
> > there something else we have to build? We are already using the
> > latest
> > httpclient (httpclient5-5.0-beta5)
> >
> > Thanks,
> > Joan.
> >
> > -Original Message-
> > From: Oleg Kalnichevski
> > Sent: Friday, August 23, 2019 9:49 AM
> > To: HttpClient User Discussion
> > Subject: Re: Issue sending https to an http endpoint
> >
> > On Thu, 2019-08-22 at 23:12 +0200, Joan grupoventus wrote:
> > > Hi Oleg,
> > >
> > > Well, not sure what's happening. In "our" git
> > > (https://github.com/joanbalaguero/HttpClient) I have
> > > uploaded 4
> > > files that connect by https to the problematic url.
> > >
> > > The "TestSync" is using a sync http5 client and works, ends with
> > > an
> > > exception "javax.net.ssl.SSLException: Unrecognized SSL message,
> > > plaintext connection?"
> > > The " TestAsync41ResponseConsumer.java" is using the async http
> > > 4.1.3
> > > client with an "HttpAsyncResponseConsumer" and works, ends with
> > > an
> > > exception
> > > "javax.net.ssl.SSLException: Unrecognized SSL message, plaintext
> > > connection?"
> > >
> > > The "TestAsync5FutureCallback" and "TestAsync5ResponseConsumer"
> > > are
> > > using an async http5 client (httpclient5-5-beta5 and
> > > httpcore5-5-beta9), the first one with a
> > > "FutureCallback" and the second with a
> > > "AsyncResponseConsumer". Both hang forever.
> > >
> > > So if this is not a bug in http5, what's wrong with these two
> > > last
> > > samples?
> > > The code there is minimal.
> > >
> >
> > Joan,
> >
> > I see nothing wrong with those samples and they all work for me
> > (HttpClient 5.0b5 + HttpCore 5.0b9-SNAPSHOT).
> >
> > Oleg
> > ---
> > 2019-08-23 09:46:30,669 DEBUG
> > [main][org.apache.hc.client5.http.impl.async.InternalHttpAsyncClien
> > t]
> > ex-0001: preparing request execution
> > 2019-08-23 09:46:30,676 DEBUG
> > [main][org.apache.hc.client5.http.protocol.RequestAddCookies]
> > CookieSpec selected: standard
> > 2019-08-23 09:46:30,680 DEBUG
> > [main][org.apache.hc.client5.http.protocol.RequestAuthCache] Auth
> > cache not set in the context
> > 2019-08-23 09:46:30,680 DEBUG
> > [main][org.apache.hc.client5.http.impl.async.AsyncProtocolExec] ex-
> > 0001: target auth state: UNCHALLENGED
> > 2019-08-23 09:46:30,681 DEBUG
> > [main][org.apache.hc.client5.http.impl.async.AsyncProtocolExec] ex-
> > 0001: proxy auth state: UNCHALLENGED
> > 2019-08-23 09:46:30,683 DEBUG
> > [main][org.apache.hc.client5.http.impl.async.AsyncConnectExec] ex-
> > 0001: acquiring connection with route {s}->
> > https://54.38.179.182:8083
> > 2019-08-23 09:46:30,684 DEBUG
> > [main][org.apache.hc.client5.http.impl.async.InternalHttpAsyncClien
> > t]
> > ex-0001: acquiring endpoint (3 MINUTES)
> > 2019-08-23 09:46:30,685 DEBUG
> > [main][org.apache.hc.client5.http.impl.nio.PoolingAsyncClientConnec
> > ti
> > onManager] ex-0001: endpoint lease request (3 MINUTES) [route:
> > {s}->https://54.38.179.182:8083][total kept alive: 0; route
> > allocated: 0 of 5; total allocated: 0 of 25]
> > 2019-08-23 09:46:30,689 DEBUG
> > [main][org.apache.hc.client5.http.impl.nio.PoolingAsyncClientConnec
> > ti
> > onManager] ex-0001: endpoint leased [route: {s}->
> > https://54.38.179.182:8083][total kept alive: 0; route allocated: 1
> > of
> > 5; total allocated: 1 of 25]
> > 2019-08-23 09:46:30,690 DEBUG
> > [main][org.apache.hc.client5.http.impl.nio.PoolingAsyncClientConnec
> > ti
> > onManager] ex-0001: acquired ep-
> > 2019-08-23 09:46:30,690 DEBUG
> > [main][org.apache.hc.client5.http.impl.async.InternalHttpAsyncClien
> > t]
> > ex-0001: acquired endpoint ep-
> > 2019-08-23 09:46:30,691 DEBUG
> > [main][org.apache.hc.client5.http.impl.async.InternalHttpAsyncClien
> > t]
> > ep-: connecting endpoint (3 MINUTES)
> > 2019-08-23 09:46:30,692 DEBUG
> > [main][org.apache.hc.client5.http.impl.nio.PoolingAsyncClientConnec
> > ti
> > onManager] ep-: connecting endpoint to
> > https://54.38.179.182:8083 (3
RE: Issue sending https to an http endpoint
Hi Oleg,
I uploaded the httpcore-5b9 we generated to the git. Is it possible you
download it and try just one test with async Http5 to check if it works for you?
We have checked the jar and it seems to be correct, so if you are using the
same version I don't understand why it works for you and not for us.
Thanks,
Joan.
-Original Message-
From: Oleg Kalnichevski
Sent: Friday, August 23, 2019 5:32 PM
To: HttpClient User Discussion
Subject: Re: Issue sending https to an http endpoint
On Fri, 2019-08-23 at 17:24 +0200, Joan grupoventus wrote:
> Hi Oleg,
>
> Is this the right link to build the httpcore-b9?
> https://github.com/apache/httpcomponents-core
>
Yes, it is.
Oleg
> We checked the version of our jar and it seems to be correctly. Is
> there something else we have to build? We are already using the latest
> httpclient (httpclient5-5.0-beta5)
>
> Thanks,
> Joan.
>
> -Original Message-
> From: Oleg Kalnichevski
> Sent: Friday, August 23, 2019 9:49 AM
> To: HttpClient User Discussion
> Subject: Re: Issue sending https to an http endpoint
>
> On Thu, 2019-08-22 at 23:12 +0200, Joan grupoventus wrote:
> > Hi Oleg,
> >
> > Well, not sure what's happening. In "our" git
> > (https://github.com/joanbalaguero/HttpClient) I have uploaded 4
> > files that connect by https to the problematic url.
> >
> > The "TestSync" is using a sync http5 client and works, ends with an
> > exception "javax.net.ssl.SSLException: Unrecognized SSL message,
> > plaintext connection?"
> > The " TestAsync41ResponseConsumer.java" is using the async http
> > 4.1.3
> > client with an "HttpAsyncResponseConsumer" and works, ends with an
> > exception
> > "javax.net.ssl.SSLException: Unrecognized SSL message, plaintext
> > connection?"
> >
> > The "TestAsync5FutureCallback" and "TestAsync5ResponseConsumer"
> > are
> > using an async http5 client (httpclient5-5-beta5 and
> > httpcore5-5-beta9), the first one with a
> > "FutureCallback" and the second with a
> > "AsyncResponseConsumer". Both hang forever.
> >
> > So if this is not a bug in http5, what's wrong with these two last
> > samples?
> > The code there is minimal.
> >
>
> Joan,
>
> I see nothing wrong with those samples and they all work for me
> (HttpClient 5.0b5 + HttpCore 5.0b9-SNAPSHOT).
>
> Oleg
> ---
> 2019-08-23 09:46:30,669 DEBUG
> [main][org.apache.hc.client5.http.impl.async.InternalHttpAsyncClient]
> ex-0001: preparing request execution
> 2019-08-23 09:46:30,676 DEBUG
> [main][org.apache.hc.client5.http.protocol.RequestAddCookies]
> CookieSpec selected: standard
> 2019-08-23 09:46:30,680 DEBUG
> [main][org.apache.hc.client5.http.protocol.RequestAuthCache] Auth
> cache not set in the context
> 2019-08-23 09:46:30,680 DEBUG
> [main][org.apache.hc.client5.http.impl.async.AsyncProtocolExec] ex-
> 0001: target auth state: UNCHALLENGED
> 2019-08-23 09:46:30,681 DEBUG
> [main][org.apache.hc.client5.http.impl.async.AsyncProtocolExec] ex-
> 0001: proxy auth state: UNCHALLENGED
> 2019-08-23 09:46:30,683 DEBUG
> [main][org.apache.hc.client5.http.impl.async.AsyncConnectExec] ex-
> 0001: acquiring connection with route {s}->
> https://54.38.179.182:8083
> 2019-08-23 09:46:30,684 DEBUG
> [main][org.apache.hc.client5.http.impl.async.InternalHttpAsyncClient]
> ex-0001: acquiring endpoint (3 MINUTES)
> 2019-08-23 09:46:30,685 DEBUG
> [main][org.apache.hc.client5.http.impl.nio.PoolingAsyncClientConnecti
> onManager] ex-0001: endpoint lease request (3 MINUTES) [route:
> {s}->https://54.38.179.182:8083][total kept alive: 0; route
> allocated: 0 of 5; total allocated: 0 of 25]
> 2019-08-23 09:46:30,689 DEBUG
> [main][org.apache.hc.client5.http.impl.nio.PoolingAsyncClientConnecti
> onManager] ex-0001: endpoint leased [route: {s}->
> https://54.38.179.182:8083][total kept alive: 0; route allocated: 1 of
> 5; total allocated: 1 of 25]
> 2019-08-23 09:46:30,690 DEBUG
> [main][org.apache.hc.client5.http.impl.nio.PoolingAsyncClientConnecti
> onManager] ex-0001: acquired ep-
> 2019-08-23 09:46:30,690 DEBUG
> [main][org.apache.hc.client5.http.impl.async.InternalHttpAsyncClient]
> ex-0001: acquired endpoint ep-
> 2019-08-23 09:46:30,691 DEBUG
> [main][org.apache.hc.client5.http.impl.async.InternalHttpAsyncClient]
> ep-: connecting endpoint (3 MINUTES)
> 2019-08-23 09:46:30,692 DEBUG
> [main][org.apache.hc.client5.http.impl.nio.PoolingAsyncClientConnecti
> onManager] ep-: connecting endpoint to
> https://54.38.179.182:8083 (3 MINUTES)
> 2019-08-23 09:46:30,692 DEBUG
> [main][org.apache.hc.client5.http.impl.nio.MultihomeIOSessionRequeste
> r] https://54.38.179.182:8083: resolving remote address
> 2019-08-23 09:46:30,692 DEBUG
> [main][org.apache.hc.client5.http.impl.nio.MultihomeIOSessionRequeste
> r] https://54.38.179.182:8083: resolved to [/54.38.179.182]
> 2019-08-23 09:46:30,693 DEBUG
> [main][org.apache.hc.client5.http.impl.nio.MultihomeIOSessionRequeste
> r]
