Mailing-List: contact dev-help@hc.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "HttpComponents Project" <dev@hc.apache.org>
Message-ID: <1520146690.1257346172407.JavaMail.jira@brutus>
Date: Wed, 4 Nov 2009 14:49:32 +0000 (UTC)
From: "Oleg Kalnichevski (JIRA)" <jira@apache.org>
To: dev@hc.apache.org
Subject: [jira] Resolved: (HTTPCLIENT-886) Incorrect handling of
 NoHttpResponseException in DefaultHttpMethodRetryHandler
In-Reply-To: <739382851.1257338972954.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/HTTPCLIENT-886?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Oleg Kalnichevski resolved HTTPCLIENT-886.
------------------------------------------

    Resolution: Invalid

(1) There will be no fixes to HttpClient 3.x other than for severe security related issues. Please do not re-open the issue unless the problem can be reproduced with HttpClient 4.0 

(2) It is not a problem of HttpClient if your application abuses HTTP protocol for something it has never been intended for, such as transaction processing. 

Oleg


> Incorrect handling of NoHttpResponseException in DefaultHttpMethodRetryHandler
> ------------------------------------------------------------------------------
>
>                 Key: HTTPCLIENT-886
>                 URL: https://issues.apache.org/jira/browse/HTTPCLIENT-886
>             Project: HttpComponents HttpClient
>          Issue Type: Bug
>    Affects Versions: 3.1 Final
>            Reporter: Sylvain Laurent
>
> We have a buggy load-balancer that sometimes forwards the request to the back-end server, and then close the connections without returning any data at all.
> This provokes a NoHttpResponseException inside commons http client 3.1, which is handled by DefaultHttpMethodRetryHandler.
> Unfortunately DefaultHttpMethodRetryHandler handles this NoHttpResponseException by asking for a retry. In our case, this is very dangerous because the request has already been sent and is being processed by the back-end server.
> I think that in the case of a NoHttpResponseException the test !method.isRequestSent() shoud be done :
>         if (exception instanceof NoHttpResponseException && !method.isRequestSent()) {
>             // Retry if the server dropped connection on us AND the request was not sent
>             return true;
>         }

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@hc.apache.org
For additional commands, e-mail: dev-help@hc.apache.org