On 12/05/2023 15:27, Oleg Kalnichevski wrote:
On Fri, 2023-05-12 at 15:25 +0100, thc...@gmail.com wrote:
On 12/05/2023 14:47, Oleg Kalnichevski wrote:
On Fri, 2023-05-12 at 14:17 +0100, thc...@gmail.com wrote:
On 12/05/2023 13:27, Oleg Kalnichevski wrote:
On Fri, 2023-05-12 at 11:48 +0
On 12/05/2023 14:47, Oleg Kalnichevski wrote:
On Fri, 2023-05-12 at 14:17 +0100, thc...@gmail.com wrote:
On 12/05/2023 13:27, Oleg Kalnichevski wrote:
On Fri, 2023-05-12 at 11:48 +0200, Joan grupoventus wrote:
Hi Oleg,
After changing this method from:
private TlsStrategy getTLSStrategy()
On 12/05/2023 13:27, Oleg Kalnichevski wrote:
On Fri, 2023-05-12 at 11:48 +0200, Joan grupoventus wrote:
Hi Oleg,
After changing this method from:
private TlsStrategy getTLSStrategy() throws Exception {
return (DefaultClientTlsStrategy.getDefault());
}
To:
private TlsStrategy getTLSStrat
Hi.
From the Chapter 3 of "HttpClient Tutorial" [1] it seems that that can
be achieved by registering a CookieSpecProvider [2], for example, and
using BestMatchSpecFactory [3]:
Registry r = RegistryBuilder.
create()
// override default behaviour of BEST_MATCH (2nd arg of
BestMatchSpec
Hi.
> One thing I forget to add which might of use, my application is acting as a
> proxy in here. It accepts requests from a client and proxies it to a server
> thus manually getting all the headers and setting the headers manually in the
> HttpClient.
(I will assume that the cookie managemen
Hi.
> That's why I though this was something related to Http pool, as if the
> connections were not expired. But if you say that you don't print these
> messages, then I am a bit lost (because tomcat guys also say that they don't
> print these messages, and me neither).
Those messages looks a
