Re: Help with async client

On Thu, 2016-03-17 at 17:51 +0100, Joan Balagueró wrote: > Hello, > > I hope this is the last question ... On our proxy we are reading the response > from the backend with a FutureCallback. On the complete method, > we process the response body in this way: > > public void

Re: Spurious blank line being added to headers...

Are you sure that value of the X-CREDENTIALS header doesn't end with \r\n ? On Thu, Mar 17, 2016 at 11:16 PM, Gordon Ross wrote: > I’m using HttpClient 4.3.6 on Java 1.7.0_95. I’m finding that in certain > circumstances, HttpClient is adding a spurious blank line to the

Re: [4.3.3] Newbie question about Stale Check

We upgraded to 4.5.2 and we are seeing only 200 SocketTimeoutExceptions now. Thanks Oleg -- View this message in context: http://httpcomponents.10934.n7.nabble.com/4-3-3-Newbie-question-about-Stale-Check-tp28119p28148.html Sent from the HttpClient-User mailing list archive at Nabble.com.

Re: Help with async client

On Thu, 2016-03-17 at 10:42 +0100, Joan Balagueró wrote: > Hi Oleg, > > Thanks. If I have a 400ms connection timeout and a 850ms response timeout, I > understand that the select interval must contain the 400ms (the lowest > value). True? > Yes. > In our app these connection/response timeouts

Re: Help with async client

On Wed, 2016-03-16 at 15:41 +0100, Joan Balagueró wrote: > Hi Oleg, > > Finally the issue was nothing to do with the async client. > > Now we are experimenting with connection and response timeouts, setting just > 1ms for both. In the blocking client, we get connection and response timeouts >

RE: Help with async client

Hello, I hope this is the last question ... On our proxy we are reading the response from the backend with a FutureCallback. On the complete method, we process the response body in this way: public void completed(HttpResponse objResponse) { HttpEntity entity = null; try {

RE: Help with async client

Hi Oleg, Finally the issue was nothing to do with the async client. Now we are experimenting with connection and response timeouts, setting just 1ms for both. In the blocking client, we get connection and response timeouts for all requests we send. But with the async client we are not able to

RE: WinHttpClients

Thanks. I will use it with a bit of caution then. I appreciate their being around, but understand the support issues. Mark Disclaimer: The opinions provided herein do not necessarily state or reflect those of Donnell Systems, Inc.(DSI). DSI makes no warranty for and assumes no legal

RE: Help with async client

Hi Oleg, Thanks. If I have a 400ms connection timeout and a 850ms response timeout, I understand that the select interval must contain the 400ms (the lowest value). True? In our app these connection/response timeouts can be modified on the fly. That's why we are using a request config, and

Spurious blank line being added to headers...

I’m using HttpClient 4.3.6 on Java 1.7.0_95. I’m finding that in certain circumstances, HttpClient is adding a spurious blank line to the headers. This is then causing the far end server to treat the remaining headers as the body - not what is desired! If I run the code as a stand alone Java