Return-Path: Delivered-To: apmail-hc-httpclient-users-archive@www.apache.org Received: (qmail 63222 invoked from network); 19 Mar 2008 19:54:28 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 19 Mar 2008 19:54:28 -0000 Received: (qmail 18695 invoked by uid 500); 19 Mar 2008 19:54:25 -0000 Delivered-To: apmail-hc-httpclient-users-archive@hc.apache.org Received: (qmail 18681 invoked by uid 500); 19 Mar 2008 19:54:25 -0000 Mailing-List: contact httpclient-users-help@hc.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: "HttpClient User Discussion" Delivered-To: mailing list httpclient-users@hc.apache.org Received: (qmail 18672 invoked by uid 99); 19 Mar 2008 19:54:25 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 19 Mar 2008 12:54:25 -0700 X-ASF-Spam-Status: No, hits=1.2 required=10.0 tests=SPF_NEUTRAL X-Spam-Check-By: apache.org Received-SPF: neutral (nike.apache.org: local policy) Received: from [217.150.250.44] (HELO ok2consulting.nine.ch) (217.150.250.44) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 19 Mar 2008 19:53:36 +0000 Received: from [192.168.1.100] (84-75-108-49.dclient.hispeed.ch [84.75.108.49]) by ok2consulting.nine.ch (Postfix) with ESMTP id 6B580198402; Wed, 19 Mar 2008 20:53:56 +0100 (CET) Subject: Re: Trouble shooting informational status From: Oleg Kalnichevski To: HttpClient User Discussion Cc: contact@noelios.com In-Reply-To: References: Content-Type: text/plain Date: Wed, 19 Mar 2008 20:53:56 +0100 Message-Id: <1205956436.5825.17.camel@ubuntu> Mime-Version: 1.0 X-Mailer: Evolution 2.12.1 Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org On Wed, 2008-03-19 at 14:31 +0100, Thierry Boileau wrote: > Hello all, > > After some tests, I noticed that the HttpClient hangs in the case the > server sends a response with informational status and at the same time > does not support persistent connections. I recognize that this case is > quite unusual or unpractical however it leads to block the client. > > I wonder if the behaviour of the > org.apache.commons.httpclient.HttpMethodBase#readResponse method could > not be improved by just adding a call to the "shouldCloseConnection" > method after checking sthe status code. > if ((status >= 100) && (status < 200)) { > if(shouldCloseConnection(conn)){ > break; > } > > best regards, > Thierry Boileau > Thierry, We no longer fix all but most serious bugs in the 3.x codeline. Please test against the latest 4.0 release or better the SVN snapshot. Oleg > --------------------------------------------------------------------- > To unsubscribe, e-mail: httpclient-users-unsubscribe@hc.apache.org > For additional commands, e-mail: httpclient-users-help@hc.apache.org > --------------------------------------------------------------------- To unsubscribe, e-mail: httpclient-users-unsubscribe@hc.apache.org For additional commands, e-mail: httpclient-users-help@hc.apache.org