In my test scenario the first read operation is blocked. The java.net.SocketTimeoutException only came after 2x of the timeout. I'm using a slow responding http server, that pumps out the headers and the beginning of the response fast, but stalls before reaching the full content length.
Is it possible HttpcClient swallows one java.net.SocketTimeoutException and retries the read operation? -- View this message in context: http://www.nabble.com/-HttpClient--Timeout-appears-to-be-twice-of-requested-tf2046358.html#a5638412 Sent from the Commons - User forum at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
