Re: Server-side mid-air connection close on upload

On Tue, 2020-06-02 at 11:09 +0200, Michael Osipov wrote: > Am 2020-06-02 um 00:09 schrieb Michael Osipov: > > Am 2020-06-01 um 15:11 schrieb Oleg Kalnichevski: > > > On Sun, 2020-05-31 at 23:13 +0200, Michael Osipov wrote: > > > > Am 2020-05-30 um 22:53 schrieb Oleg

Re: Server-side mid-air connection close on upload

On Sun, 2020-05-31 at 23:13 +0200, Michael Osipov wrote: > Am 2020-05-30 um 22:53 schrieb Oleg Kalnichevski: > > On Sat, 2020-05-30 at 21:58 +0200, Michael Osipov wrote: > > ... > > > > Now we need to decide if this is as good as it gets or we want > > > &g

Re: Server-side mid-air connection close on upload

On Sat, 2020-05-30 at 21:58 +0200, Michael Osipov wrote: > ... > > #isDataAvailable is not cheap even with 1 ms timeout. Socket > > timeout > > granularity is far from being 1 ms. In fact it is pretty close to > > 50 > > ms. If we are not careful we can easily end up with 50 ms overhead > > for

Re: Server-side mid-air connection close on upload

On Fri, 2020-05-29 at 00:46 +0200, Michael Osipov wrote: > Am 2020-05-28 um 22:51 schrieb Oleg Kalnichevski: > > On Thu, 2020-05-28 at 22:01 +0200, Michael Osipov wrote: > > > Am 2020-05-28 um 10:40 schrieb Oleg Kalnichevski: > > > > On Thu, 2020-05-28 at 00:

Re: Server-side mid-air connection close on upload

On Thu, 2020-05-28 at 22:01 +0200, Michael Osipov wrote: > Am 2020-05-28 um 10:40 schrieb Oleg Kalnichevski: > > On Thu, 2020-05-28 at 00:02 +0200, Michael Osipov wrote: > > > > > > > > > ... > > > > > > Please try out this patch. This sho

Re: Server-side mid-air connection close on upload

On Thu, 2020-05-28 at 00:02 +0200, Michael Osipov wrote: > ... > > Please try out this patch. This should now give us proper out of > > sequence response check with minimal overhead. The check will now > > be > > performed for chunks of 2048 bytes instead of each and every write > >

Re: Server-side mid-air connection close on upload

On Wed, 2020-05-27 at 22:14 +0200, Oleg Kalnichevski wrote: > On Wed, 2020-05-27 at 21:10 +0200, Michael Osipov wrote: > > Am 2020-05-27 um 19:13 schrieb Oleg Kalnichevski: > > > On Wed, 2020-05-27 at 18:26 +0200, Mi

Re: Server-side mid-air connection close on upload

On Wed, 2020-05-27 at 21:10 +0200, Michael Osipov wrote: > Am 2020-05-27 um 19:13 schrieb Oleg Kalnichevski: > > On Wed, 2020-05-27 at 18:26 +0200, Michael Osipov wrote: > > > > > > > ... > > > > > > > &g

Re: Server-side mid-air connection close on upload

On Wed, 2020-05-27 at 18:26 +0200, Michael Osipov wrote: > ... https://github.com/ok2c/httpcomponents-core/commit/732a99563e73529e0359625fda54351b843b2e34 > > This patch does not work (reliably): > > * I have never seen EarlyResponseException > * When run over HTTPS I see early responses

Re: Server-side mid-air connection close on upload

On Wed, 2020-05-27 at 14:32 +0200, Oleg Kalnichevski wrote: > ... > https://github.com/apache/httpcomponents-client/commit/a554aadabafe26ae5412b26a311ffa105e623cc2 > > > > Tried with various timeouts, 5 ms, 15 ms, 25 ms, 50 ms, 500 ms. > > Connections are correctly

Re: Server-side mid-air connection close on upload

On Wed, 2020-05-27 at 14:23 +0200, Michael Osipov wrote: > Am 2020-05-27 um 12:14 schrieb Oleg Kalnichevski: > > On Wed, 2020-05-27 at 00:01 +0200, Michael Osipov wrote: > > > Am 2020-05-26 um 23:09 schrieb Oleg Kalnichevski: > > > > On Tue, 2020-05-26 at 22:

Re: Server-side mid-air connection close on upload

On Wed, 2020-05-27 at 00:01 +0200, Michael Osipov wrote: > Am 2020-05-26 um 23:09 schrieb Oleg Kalnichevski: > > On Tue, 2020-05-26 at 22:28 +0200, Michael Osipov wrote: > > > Am 2020-05-26 um 20:20 schrieb Oleg Kalnichevski: > > > > On Tue, 2020-05-26 at 17:5

Re: Server-side mid-air connection close on upload

On Wed, 2020-05-27 at 11:48 +0200, Michael Osipov wrote: > Am 2020-05-27 um 11:39 schrieb Oleg Kalnichevski: > > On Wed, 2020-05-27 at 00:01 +0200, Michael Osipov wrote: > > > > > > > > > ... > > > > > So far, the patch works and I can acc

Re: Server-side mid-air connection close on upload

On Wed, 2020-05-27 at 00:01 +0200, Michael Osipov wrote: > ... > So far, the patch works and I can access the first 401 response. > I found a pretty nasty bug in HttpClient that leads to re-use of connections after request termination. I am working on a fix. Oleg

Re: Server-side mid-air connection close on upload

On Tue, 2020-05-26 at 22:28 +0200, Michael Osipov wrote: > Am 2020-05-26 um 20:20 schrieb Oleg Kalnichevski: > > On Tue, 2020-05-26 at 17:58 +, Bernd Eckenfels wrote: > > > Michael, this looks a bit like the packets in between have been > > > TLS > > > ha

Re: Server-side mid-air connection close on upload

_ > Von: Michael Osipov > Gesendet: Dienstag, Mai 26, 2020 7:53 PM > An: HttpClient User Discussion > Betreff: Re: Server-side mid-air connection close on upload > > Am 2020-05-26 um 09:14 schrieb Oleg Kalnichevski: > > On M

Re: Server-side mid-air connection close on upload

On Mon, 2020-05-25 at 11:56 +0200, Michael Osipov wrote: > ... > Where long denotes the min size of the request body and Timeout how > long > we want to wait for the early response. > > Let me know if you have somthing to test, setup is there at work. > Hi Michael Please try out this

Re: Server-side mid-air connection close on upload

On Mon, 2020-05-25 at 11:45 +0200, Michael Osipov wrote: > Am 2020-05-25 um 09:47 schrieb Oleg Kalnichevski: > > On Sat, 2020-05-23 at 01:10 +0200, Michael Osipov wrote: > > > > > > > > ... > > > > > Am 2020-05-22 um 22:18 schrieb Oleg Kaln

Re: Server-side mid-air connection close on upload

On Sat, 2020-05-23 at 01:10 +0200, Michael Osipov wrote: > > ... > Am 2020-05-22 um 22:18 schrieb Oleg Kalnichevski: > > Theoretically we could enhance the classic client-side protocol > > handler > > to check if the length of the request entity is known and is >

Re: Server-side mid-air connection close on upload

() to test for an out of sequence response is actually an interesting idea. I will experiment with it in the coming days. Thank you! Oleg > Gruss > Bernd > -- > http://bernd.eckenfels.net > ____ > Von: Oleg Kalnichevski > Gesendet: Friday, May

Re: Server-side mid-air connection close on upload

On Fri, 2020-05-22 at 19:25 +0200, Michael Osipov wrote: > Hi folks, > > I believe that this is a wellknown limitation in blocking I/O, but > would > like to know how to solve/workaround this issue. The source > discussion > is here [1]. > > Bascially, I am posting a large file (~7 MB) to

Re: SNI for http core v5 server (non-async)

ally has two lines of code. What is the point of extending it? Oleg > > On Wed, May 20, 2020 at 7:05 AM Oleg Kalnichevski > wrote: > > > On Tue, 2020-05-19 at 21:25 -0400, C c wrote: > > > I looked at emails and docs and can't find a trail on getting > > > starte

Re: SNI for http core v5 server (non-async)

On Tue, 2020-05-19 at 21:25 -0400, C c wrote: > I looked at emails and docs and can't find a trail on getting started > w/ > SNI. > > In netty, I can set up SNI to look up what domain is being requested > so I > can use a cert to the non-async server so I can serve multiple > domains with >

Re: After 100,000's of requests, I start getting status code 400 bad request for all requests

On Tue, 2020-05-19 at 11:39 -0500, Nicholas DiPiazza wrote: > Yep Kerberos is an option. If I get desperate. > Kerberos support is even worse. One ought to be using HTTP basic over TLS or digest. Oleg > > > On Tue, May 19, 2020 at 10:28 AM Oleg Kalnichevski > wrote: >

Re: After 100,000's of requests, I start getting status code 400 bad request for all requests

On Tue, May 19, 2020 at 8:06 AM Oleg Kalnichevski > wrote: > > > On Mon, 2020-05-18 at 20:24 -0500, Nicholas DiPiazza wrote: > > > Hey HTTP client users list! > > > > > > I've got some strange behavior going on and could use some help > > > sorting

Re: After 100,000's of requests, I start getting status code 400 bad request for all requests

On Mon, 2020-05-18 at 20:24 -0500, Nicholas DiPiazza wrote: > Hey HTTP client users list! > > I've got some strange behavior going on and could use some help > sorting it > out. > > I created a reproducer project of the code that I am using to access > HTTP > client: >

Re: HTTP/2 connection gets closed and won't be reopened

On Thu, 2020-05-14 at 13:59 +0200, u...@natune.net.INVALID wrote: > > I need to see the original exception with a full stack trace that > > caused the i/o reactor to shut down and preferably the complete > > session > > log leading to that condition. > > > > Oleg > > I was unable to get

Re: HTTP/2 connection gets closed and won't be reopened

On Thu, 2020-05-14 at 10:53 +0200, u...@natune.net.INVALID wrote: > > > While using HTTP/2 only client, after approx. 12 hours the > > > connection > > > is > > > broken and is not established anymore. Every couple of minutes > > > async > > > HTTP/2 requests are sent to a Tomcat9 server. There

Re: HTTP/2 connection gets closed and won't be reopened

On Wed, 2020-05-13 at 19:23 +0200, u...@natune.net.INVALID wrote: > Hello, > > While using HTTP/2 only client, after approx. 12 hours the connection > is > broken and is not established anymore. Every couple of minutes async > HTTP/2 requests are sent to a Tomcat9 server. There are no errors >

Re: How to HttpRequest. getIPAddress() ?

On Sat, 2020-05-09 at 19:48 -0400, C c wrote: > Hi, I'm sure this has been asked before, but the mail search found no > results. > I'm using latest version 5. > How do I get the IP address other than the headers? IP address is not a property of the request. It is a property of the endpoint used

Re: Testing support for HttpClient.

You will have to port it to 5.0 APIs first though. There will be no new features in the 4.5.x code line. Oleg > Regards > Paweł Adamski > > > niedz., 3 maj 2020 o 17:42 Oleg Kalnichevski > napisał(a): > > > On Sun, 2020-05-03 at 16:39 +0200, Paweł Adamski wrote: &

Re: Testing support for HttpClient.

On Sun, 2020-05-03 at 16:39 +0200, Paweł Adamski wrote: > Hi > My name is Paweł. I'm an author of the library for easy mocking > HttpClient > ( https://github.com/PawelAdamski/HttpClientMock ). I would like to > ask > about your opinion wherever it would be a good idea to include it as > an >

[ANNOUNCEMENT] HttpComponents Client 4.5.12 GA Released

The Apache HttpComponents project is pleased to announce 4.5.12 GA release of HttpComponents HttpClient. This is a maintenance release that fixes a regression introduced by the previous release that caused rejection of certificates with non- standard domains. Download -

Re: Control behavior of Caching based on response

On Thu, 2020-02-27 at 14:01 -0800, Novice User wrote: > Hi, > > We’re using HTTPClient 4.5.11 with caching enabled to make HTTP GET > calls to our provider. > > The provider returns JSON object and as JSON can miss some keys in > some cases, we want to treat it as bad data and avoid it being >

Re: use a custom AbstractConnPool

On Tue, 2020-02-25 at 17:24 -0800, Clément Guillaume wrote: > Hello, > > Is it possible to pass a custom AbstractConnPool to > PoolingHttpClientConnectionManager? > I would like to use something like the default CPool with some > custom onLease, onRelease and onReuse. > > Thank you, > > Clement

[ANNOUNCEMENT] HttpComponents Client 5.0 GA released

The Apache HttpComponents project is pleased to announce 5.0 GA release of HttpComponents Client. This is the first stable (GA) release of HttpClient 5.0. Notable changes and features included in the 5.0 series are: * Support for the HTTP/2 protocol and conformance to requirements and

Re: Possible bug in RedirectExec in HttpClient 5.0-beta7

On Thu, 2020-02-20 at 20:36 +0100, Michael Osipov wrote: > Am 2020-02-20 um 10:50 schrieb Oleg Kalnichevski: > > On Wed, 2020-02-19 at 21:19 +0100, Michael Osipov wrote: > > > Am 2020-02-18 um 22:29 schrieb Oleg Kalnichevski: > > > > On Tue, 2020-02-18 at 20:

Re: Fail non-repeatable requests when following redirects

On Thu, 2020-02-20 at 19:46 +0100, Michael Osipov wrote: > Am 2020-02-19 um 13:42 schrieb Oleg Kalnichevski: > > ... > > > > > > Hi Michael > > > > > > > > I can take a look. Is there a test case I could run locally to > > > >

Re: Possible bug in RedirectExec in HttpClient 5.0-beta7

On Wed, 2020-02-19 at 21:19 +0100, Michael Osipov wrote: > Am 2020-02-18 um 22:29 schrieb Oleg Kalnichevski: > > On Tue, 2020-02-18 at 20:35 +0100, Michael Osipov wrote: > > > Am 2020-02-18 um 10:07 schrieb Oleg Kalnichevski: > > > > On Mon, 2020-02-17 at 21:

Re: Fail non-repeatable requests when following redirects

... > > Hi Michael > > > > I can take a look. Is there a test case I could run locally to > > reproduce the defect? > > I will try to skim this out of Wagon. Meanwhile I have attached the > failure with Wagon. You'll see that HttpClient follows the redirect, > but > is stuck (checksum files

Re: Fail non-repeatable requests when following redirects

On Tue, 2020-02-18 at 19:48 +0100, Michael Osipov wrote: > > > ... > Am 2020-02-18 um 10:50 schrieb Oleg Kalnichevski: > > On Mon, 2020-02-17 at 15:29 +0100, Michael Osipov wrote: > Sure, I have uploaded webapp.war. Please deploy it as usual on > Tomcat > an

Re: Possible bug in RedirectExec in HttpClient 5.0-beta7

On Tue, 2020-02-18 at 20:35 +0100, Michael Osipov wrote: > Am 2020-02-18 um 10:07 schrieb Oleg Kalnichevski: > > On Mon, 2020-02-17 at 21:28 +0100, Michael Osipov wrote: > > > Folks, > > > > > > I have continued to fiddle a bit more with the redirector i

Re: Fail non-repeatable requests when following redirects

On Mon, 2020-02-17 at 15:29 +0100, Michael Osipov wrote: > Am 2020-02-17 um 14:11 schrieb Oleg Kalnichevski: > > On Sun, 2020-02-16 at 23:30 +0100, Michael Osipov wrote: > > > Folks, > > > > > > I am working again on some stuff in Maven Wagon, WAGON-57

Re: Possible bug in RedirectExec in HttpClient 5.0-beta7

On Mon, 2020-02-17 at 21:28 +0100, Michael Osipov wrote: > Folks, > > I have continued to fiddle a bit more with the redirector in > HttpClient > 5.0. I have modified my servlet code to respond with 307 from within > a > Tomcat valve which immediately kicks in after "Expect: 100-continue". > >

[ANNOUNCEMENT] HttpComponents Core 5.0 GA Released

The Apache HttpComponents project is pleased to announce 5.0 GA release of HttpComponents Core. This is the first stable (GA) release of HttpCore 5.0. Notable changes and features included in the 5.0 series: * Support for HTTP/2 protocol and conformance to requirements and recommendations of

Re: Fail non-repeatable requests when following redirects

On Sun, 2020-02-16 at 23:30 +0100, Michael Osipov wrote: > Folks, > > I am working again on some stuff in Maven Wagon, WAGON-570. After > some > tests I do not understand why this does not fail: > > > main] DEBUG org.apache.http.headers - http-outgoing-0 >> PUT /test- > > secured-put-resource

Re: SocketTimeoutExceptions When Communicating with a Load Balancer

On Mon, 2020-02-10 at 23:25 -0500, Evan J wrote: > Hi, > > (looks like I'd sent this to a wrong user group originally) > > We deploy an application B (which is basically a backend application > serving a web application) to a cluster of application servers (JBoss > EAP > 7.2 -- 8 instances).

Re: Log any remote request made by httpClient 4.5.x

gurable by me as > well. > Disable logging for categories you do not want. Refer to the `Enable context logging for connection management / request execution` section as an example Oleg > > TIA > T > > On Mon, Jan 27, 2020 at 4:44 PM Oleg Kalnichevski > wrote: > &

Re: Log any remote request made by httpClient 4.5.x

On Mon, 2020-01-27 at 14:14 +0100, Tamás Cservenák wrote: > Howdy, > > I'd like to log ANY remote request httpClient 4.5.x does (stable), > what is > the best way to active that? (like "upstream" request log, so method > + URL > [schema://hostname/path]). > > I'd like to cover cases even like

[ANNOUNCEMENT] HttpComponents Client 5.0 beta7 (GA candidate) released

The Apache HttpComponents project is pleased to announce 5.0-beta7 release of HttpComponents Client. This BETA release upgrades HttpCore to the latest version and addresses a number of issues found since the previous BETA release. Notable changes and features in the 5.0 series:

Re: DefaultHostnameVerifier for private domains

On Mon, 2020-01-20 at 11:49 +, Daniel wrote: > Hi folks  > > I believe the recent change to > https://github.com/apache/httpcomponents-client/pull/198 broke > validation > for private domains. > The domain type is now forced to ICANN. In my scenario this causes a > valid > cert check for

[ANNOUNCEMENT] HttpComponents Client 4.5.11 GA Released

The Apache HttpComponents project is pleased to announce 4.5.11 GA release of HttpComponents HttpClient. This is a maintenance release that fixes a number defects discovered since 4.5.10 and upgrades HttpCore dependency to version 4.4.13. Download - Release

[ANNOUNCEMENT] HttpComponents Core 4.4.13 Released

The Apache HttpComponents project is pleased to announce 4.4.13 GA release of HttpComponents Core. This is a maintenance release that corrects a number of defects discovered since release 4.4.12. Please note that as of 4.4 HttpCore requires Java 1.6 or newer. Download -

[ANNOUNCEMENT] HttpComponents Core 5.0 beta11 (GA candidate) released

The Apache HttpComponents project is pleased to announce 5.0-beta11 (GA candidate) release of HttpComponents Core. This BETA improves handling of illegal or invalid requests on the server side and fixes a number of defects in HTTP/2 protocol code found since the last release. IMPORTANT: This

Re: Socket reuse question

.org/confluence/display/HttpComponents/FrequentlyAskedConnectionManagementQuestions Oleg > Regards, Tamás > > On Wed, Dec 11, 2019 at 1:31 PM Oleg Kalnichevski > wrote: > > > On Wed, 2019-12-11 at 10:50 +0100, Tamás Barta wrote: > > > Hi! > > > > > >

Re: Socket reuse question

On Wed, 2019-12-11 at 10:50 +0100, Tamás Barta wrote: > Hi! > > I'm using httpclient-4.5.2.redhat-2.jar and I have a question I hope > somebody can explain for me. > I use this simple sample code to connect to a server a few times: > > try (CloseableHttpClient client =

Re: SSL failure when using new Async APIs in 5.0-beta6

lt;<...>> > -Original Message- > From: Oleg Kalnichevski > Sent: Thursday, December 5, 2019 4:56 PM > To: HttpClient User Discussion > 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: >

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 &

Re: SSL failure when using new Async APIs in 5.0-beta6

On Tue, 2019-12-03 at 16:45 +0100, Oleg Kalnichevski wrote: > What I immediately see if that the server sends a different (broken) > SSL certificate chain during the TLS handshake with > RawSSLAsyncRegularTest example. At this point I _cannot_ confirm that > as HttpClient's fault but

Re: SSL failure when using new Async APIs in 5.0-beta6

What I immediately see if that the server sends a different (broken) SSL certificate chain during the TLS handshake with RawSSLAsyncRegularTest example. At this point I _cannot_ confirm that as HttpClient's fault but I will take a closer look tomorrow. Oleg On Tue, 2019-12-03 at 15:35 +0100,

[ANNOUNCEMENT] HttpComponents Core 5.0 beta10 (GA candidate) released

The Apache HttpComponents project is pleased to announce 5.0-beta10 (GA candidate) release of HttpComponents Core. A. This BETA fixes a bug in the HTTP/2 setting handshake implementation and a performance regression in the HTTP/1.1 protocol handler. IMPORTANT: This release is expected

Re: SO_SNDBUF/SO_RCVBUF

On Tue, 2019-10-22 at 11:49 -0400, Elliotte Rusty Harold wrote: > Where does HttpClient get its default values of SO_SNDBUF and > SO_RCVBUF from? Are these set i the code somewhere, and if so where? > > Or are they inherited from the JDK or the host OS? > > Thanks. > By default HttpCore and

Re: Advise on HttpEntity#isRepeatable()

On Tue, 2019-10-22 at 16:17 +0200, Michael Osipov wrote: > Folks, > > I am currently working on WAGON-568 and would like better understand > how > HttpEntity#isReproducible() should be properly handled. > > In AbstractHttpClientWagon#put() [1] on specific status codes the > request (PUT) is

[ANNOUNCEMENT] HttpComponents Client 5.0 beta6 (GA candidate) released

The Apache HttpComponents project is pleased to announce 5.0-beta6 release of HttpComponents Client. This BETA release picks up the latest fixes and performance improvements from HttpCore and addresses a number of issues found since the previous BETA release. IMPORTANT: This release is expected

[ANNOUNCEMENT] HttpComponents Core 5.0 beta9 (GA candidate) released

The Apache HttpComponents project is pleased to announce 5.0-beta9 (GA candidate) release of HttpComponents Core. This BETA fixes a number of defects found since the last release, improves behavior of the lax (concurrent) connection pools (special thanks to Linton Miller), simplifies and

HttpCore / HttpClient 5.0 compatibility testing

Folks I have been testing HttpCore 5.0 and HttpClient 5.0 for compatibility with common HTTP servers such as Apache HTTPD and Ngnix for quite some time using Docker containers. I also recently added httpbin.org container to the list of target test environments. The image definitions can be found

Re: max total connections

On Mon, 2019-09-23 at 10:39 +, Братухин Никита Романович wrote: > Hey there, recently we have been using this beautiful lib for our > internal microservices communication, but I have some question about > max connection count. > What will happen when max count of connections will be used? >

[ANNOUNCEMENT] HttpComponents Client 4.5.10 GA Released

The Apache HttpComponents project is pleased to announce 4.5.10 GA release of HttpComponents HttpClient. This is a maintenance release that fixes a number defects discovered since 4.5.9. Download - Release notes - <

[ANNOUNCEMENT] HttpComponents Core 4.4.12 Released

The Apache HttpComponents project is pleased to announce 4.4.12 GA release of HttpComponents Core. This is a maintenance release that corrects a number of defects discovered since release 4.4.11. Please note that as of 4.4 HttpCore requires Java 1.6 or newer. IMPORTANT: Users of HttpCore 4.x GA

Re: Issue sending https to an http endpoint

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

Re: Issue sending https to an http endpoint

omething 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:

Re: Issue sending https to an http endpoint

.apache.hc.client5.http.impl.async.InternalHttpAsyncClient] Shutdown GRACEFUL 2019-08-23 09:46:31,180 DEBUG [main][org.apache.hc.client5.http.impl.nio.PoolingAsyncClientConnectionManager] Shutdown connection pool GRACEFUL 2019-08-23 09:46:31,181 DEBUG [main][org.apache.hc.client5.http.impl.nio.Pooling

Re: Issue sending https to an http endpoint

connection?) > Thanks, > Joan. > > -Original Message- > From: Oleg Kalnichevski > Sent: Monday, August 19, 2019 9:15 AM > To: HttpClient User Discussion > Subject: Re: Issue sending https to an http endpoint > > On Sun, 2019-08-18 at 21:05 +0200, Joan grupoventus wrote:

Re: Issue sending https to an http endpoint

On Sun, 2019-08-18 at 21:05 +0200, Joan grupoventus wrote: > Hello, > > � > > A mistake made by one of our clients has brought us a possible issue > to our attention. We have been able to reproduce it on our test > environment. > > � > > The client has an endpoint that only listens on http

Re: AsyncRequestBuilder deprecated

On Thu, 2019-08-01 at 10:34 +0200, Joan grupoventus wrote: > Hello, > > � > > It seems I should use the > ‘org.apache.hc.core5.http.nio.support.AsyncRequestBuilder’ class. > Replacing the import works except for the ‘setConfig’ method that we > use to replace the connection/response timeout for

Re: How to use SSL CONNECT to the proxy with Apache HttpClient?

On Wed, 2019-07-31 at 11:32 +, Jochen Wiedmann wrote: > > On 2019/07/31 10:48:37, Oleg Kalnichevski wrote: > > > I am confused now. HttpClient always uses plain HTTP to connect to > > the > > first proxy hop. It upgrades to TLS only once the connection to the

Re: How to use SSL CONNECT to the proxy with Apache HttpClient?

On Wed, 2019-07-31 at 10:29 +, Jochen Wiedmann wrote: > > On 2019/07/31 10:06:40, Oleg Kalnichevski wrote: > > > This is depends on the connection route defined by the route > > planner. > > If the connection route in marked as secure HttpClient will attempt &g

Re: How to use SSL CONNECT to the proxy with Apache HttpClient?

On Wed, 2019-07-31 at 11:31 +0200, Jochen Wiedmann wrote: > I've got an application, which is sending a SOAP request to an > external server via a corporate proxy, which I do not control. > Sending > the request fails with a message "HTTP/1.1 500 handshakefailed". > However, sending another

Re: org.apache.hc.core5.http.NoHttpResponseException: localhost:8112 failed to respond

eIOSessionRequester.java:147) > > at > > org.apache.hc.core5.concurrent.BasicFuture.cancel(BasicFuture.java: > > 154) > > at > > org.apache.hc.core5.concurrent.BasicFuture.cancel(BasicFuture.java: > > 161) > > at > > org.apache.hc.core5.reactor.IOSession

Re: org.apache.hc.core5.http.NoHttpResponseException: localhost:8112 failed to respond

On Mon, 2019-07-22 at 12:29 +0300, Petar Tahchiev wrote: > Hello, > I have a Tomcat server running on port 8112 via HTTPS. The Tomcat has > http2 > enabled and is running with OpenJDK11. > Now when I try to connect with HTTPClient 5.0-beta5 I get this > exception: > === >

[ANNOUNCEMENT] HttpComponents Client 5.0 beta5 (GA candidate) released

The Apache HttpComponents project is pleased to announce 5.0-beta5 release of HttpComponents Client. This BETA release picks up the latest fixes and performance improvements from HttpCore and addresses a number of issues found since the previous BETA release. IMPORTANT: This release is expected

Re: Changes in handling Cyrillic characters since 4.5.8

On Wed, 2019-07-17 at 15:23 +0600, Denis Malyshkin wrote: > Hello, > > After upgrade to HttpClient version 4.5.8+ we encountered that > requests > with Cyrillic characters are broken. Below is the simple test to > expose the > issue with HttpClient version 4.5.8: >

Re: NTLM Authentication fails

or Linux? > Of course, it is. It is the default mode of operation supported by HttpClient and recommended by the project. Cheers Oleg > Best regards, > Kirill > > > > *Von:* Oleg Kalnichevski > > *Gesendet:* Mittwoch, 10. Juli 2019 15:49 > *An:* HttpClien

Re: [HttpClient 4.5.5 ]Proxy-Authorization header missing while requesting HTTPS url

On Mon, 2019-07-15 at 15:02 +0530, Kaushal Kothari wrote: > Just for clarification,I want to access the HTTPS url via proxy > server and proxy server has the basic authentication set. > > In order to authenticate,"Proxy-Authorization Basic " > header should be sent along with CONNECT request but

[ANNOUNCEMENT] HttpComponents Core 5.0 beta8 (GA candidate) released

The Apache HttpComponents project is pleased to announce 5.0-beta8 (GA candidate) release of HttpComponents Core. This BETA fixes a number of defects found since the last release and adds several convenience factory and builder classes, mainly for TLS configuration and HTTP message construction.

Re: [HttpClient 4.5.5 ]Proxy-Authorization header missing while requesting HTTPS url

On Fri, 2019-07-12 at 17:55 +0530, Kaushal Kothari wrote: > Hi Team, > > I am trying to do POC using the HttpClient 4.5.5 library and want to > access HTTPS url masked through a http proxy server with basic > authentication > and its failing. > > The authentication proxy header should be sent as

Re: TLS 1.3 with Java 11

Best, > Koji > > On Thu, Jul 11, 2019 at 7:01 PM Oleg Kalnichevski > wrote: > > > > On Thu, 2019-07-11 at 16:19 +0900, Koji Kawamura wrote: > > > Hello, > > > > > > I found a comment on in the 5.0-BETA4 release note: > > >

Re: TLS 1.3 with Java 11

On Thu, 2019-07-11 at 16:19 +0900, Koji Kawamura wrote: > Hello, > > I found a comment on in the 5.0-BETA4 release note: > > * Resolved compatibility issues with TLS 1.3 engine shipped with Java > 11 > Contributed by Oleg Kalnichevski > https://archive.apache.org/dist

Re: NTLM Authentication fails

On Mon, 2019-07-08 at 09:27 +, Kirill Rajbhandary wrote: > Dear HttpClient Support List, > > I found out that when trying to make NTLM Authentication using > httpclient-win-4.5.6.jar library it relies on > CurrentWindowsCredentials instead of using credentials provided in >

Re: Response timeout issue

On Wed, 2019-06-26 at 15:52 +0200, Joan grupoventus wrote: > Hi Oleg, > > Regarding this pending issue about response timeout, I could finally > get traces. > > Our response timeout is set to 2,000ms. This is a request that ended > up with a response timeout: >

Re: HTTP headers for Redirected HEAD requests

ent-security-policy: form-action 'none' ; report-uri > https://www.dropbox.com/csp_log?policy_name=blockserver-noscript ; > script-src 'none' > etag: 2d > x-dropbox-request-id: f260f699a530d0694879d078aeffa804 > pragma: public > cache-control: max-age=60 > referre

Re: HTTP headers for Redirected HEAD requests

ookie header: "Set-Cookie: locale=en; Domain=dropbox.com; > expires=Thu, 20 Jun 2024 17:13:32 GMT; Path=/; secure". Invalid > 'expires' attribute: Thu, 20 Jun 2024 17:13:32 GMT > 2019/06/22 10:13:32:456 PDT [WARN] ResponseProcessCookies - Invalid > cookie header: "Set-Cook

HttpClient 5.0 performance

Folks I updated my (very unscientific and biased) HttpClient benchmark [1] and got quite satisfactory results so far. https://github.com/ok2c/httpclient-benchmark/wiki Classic HttpClient 5.0 appears some 5 to 10% faster than HttpClient 4.5 and is presently the fastest. HttpAsyncClient 5.0

Re: HTTP headers for Redirected HEAD requests

On Fri, 2019-06-21 at 00:04 +, Krishna Sankaran wrote: > I am using the following java snippet for a HEAD request. The request > gets redirected couple of times, a 301 followed by 302 and dinally > gets a 200.When i use the following code snippet, i get the status as > 200 OK, however all the

[ANNOUNCEMENT] HttpComponents Client 4.5.9 GA Released

The Apache HttpComponents project is pleased to announce 4.5.9 GA release of HttpComponents HttpClient. This is a maintenance release that fixes a number defects discovered since 4.5.8. Download - Release notes -

Re: Response timeout issue

--- Oleg > Joan. > > > > Thanks, > > > > Joan. > > > > -Original Message- > > From: Oleg Kalnichevski > >

Re: Response timeout issue

lse (like updating the capacity) I have to take > into account in the ' AsyncResponseConsumer ' to avoid hanging the > execution? > I need to see a log of such 'hanging' message exchnage. Oleg > Thanks, > > Joan. > > -Original Message- > From: Oleg Kal

Re: Response timeout issue

On Thu, 2019-06-06 at 18:56 +0200, Joan grupoventus wrote: > Hi again, > > Not sure if we have seen something strange in the current test with > the keep alive connections. It's just a GET method to get a gif (this > pool has no keep-alive, that means a 100ms keep-alive). Here the > complete http

Re: Response timeout issue

On Thu, 2019-06-06 at 18:56 +0200, Joan grupoventus wrote: > Hi again, > > Not sure if we have seen something strange in the current test with > the keep alive connections. It's just a GET method to get a gif (this > pool has no keep-alive, that means a 100ms keep-alive). Here the > complete http

Re: Response timeout issue

> > -Original Message- > From: Oleg Kalnichevski > Sent: Thursday, June 6, 2019 2:27 PM > To: HttpClient User Discussion > Subject: Re: Response timeout issue > > On Wed, 2019-06-05 at 16:19 +0200, Joan grupoventus wrote: > > Hi Oleg, > > > > S

<    1   2   3   4   5   6   7   8   9   10   >