On Wed, 2007-04-11 at 14:42 +0200, Roland Weber wrote: > Hi Oleg, > > > I do not think this is the case. #exhaustInputStream() is called ONLY if > > the connection is being released back to the connection manager. > > HttpMethod#abort() simply calls HttpConnection#close(), which in its > > turn just closes down the underlying network socket without trying to > > exhaust the input stream. > > > > http://jakarta.apache. > > > org/commons/httpclient/xref/org/apache/commons/httpclient/HttpMethodBase. > > html#1102 > > http://jakarta.apache. > > > org/commons/httpclient/xref/org/apache/commons/httpclient/HttpConnection. > > html#1214 > > these are links to 3.1-RC1 code, while Tony is on 3.0.1. > Are you sure there were no improvements in that area? > > cheers, > Roland >
I am _reasonably_ sure. The 3.1 branch has seen very few changes outside the RFC2965 cookie spec and the multithreaded HTTP connection manager. Definitely nothing remotely severe as a fix for completely broken HttpMethod#abort(). Oleg --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
