Hi Thom, this is a connection keep-alive feature. The connection to the host is not closed. That doesn't mean your application can read after the response body. It only means that the open connection can be re-used for a followup request to the same host.
Have a look at documentation stuff related to keep-alive and/or connection pooling. You can send a "Connection: close" header with your request to disable keep-alive. hope that helps, Roland Thom Hehl <[EMAIL PROTECTED]> 06.10.2005 02:50 Please respond to "HttpClient User Discussion" To HttpClient User Discussion <[email protected]>, [EMAIL PROTECTED] cc Subject Should not close... OK, I've got wire logging turned on and am getting back a large XML document from my remote host. While trying to read the document I get the following lines in my log: 2005/10/05 20:46:14:046 EDT [DEBUG] HttpMethodBase - Resorting to protocol version default close connection policy 2005/10/05 20:46:14:046 EDT [DEBUG] HttpMethodBase - Should NOT close connection, using HTTP/1.1 2005/10/05 20:46:14:046 EDT [DEBUG] HttpConnection - Releasing connection back to connection manager. Then, it closes the InputStream abruptly and I get an IOException on my first read. 1) What does "Resorting to protocol version default close connection policy" mean and how can I specify the one I want to use so it doesn't change it. 2) if "Should NOT close connection, using HTTP/1.1" then why did it? Thanks! --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
