[
https://issues.apache.org/jira/browse/HTTPCLIENT-829?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12676580#action_12676580
]
Oleg Kalnichevski commented on HTTPCLIENT-829:
----------------------------------------------
Adam,
Socket timeouts are signalled as SocketTimeoutException. In case of a socket
timeout there will be no more attempts to read from the input stream. Probably
you mean end of stream condition, not a timeout?
There is basically no point fixing HttpClient 3.x, as it is nearing its end of
life.
By looking at the code I do not think HttpClient 4.0 is affected. I believe the
end of stream conditions are handled correctly. If you are able to reproduce
the problem with HttpClient 4.0, feel free to submit a patch or a test case.
Otherwise I'll close this issue as won't fix.
Oleg
> ChunkedInputStream does not handle sockets with timeouts
> --------------------------------------------------------
>
> Key: HTTPCLIENT-829
> URL: https://issues.apache.org/jira/browse/HTTPCLIENT-829
> Project: HttpComponents HttpClient
> Issue Type: Bug
> Affects Versions: 3.1 Final
> Reporter: Adam Bryzak
> Attachments: HTTPCLIENT-829.patch
>
>
> ChunkedInputStream does not handle socket timeouts when reading data. If a
> socket timeout is received after finishing reading a chunk (including it's
> CRLF combination) and before reading the next chunk's length, the next call
> to read will attempt to re-read the CRLF, causing an IOException with the
> message "CRLF expected at end of chunk" to be thrown. I have only tested this
> with 3.0 but it doesn't appear to be fixed in 3.1 or any 4.0 from looking at
> the code.
--
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: [email protected]
For additional commands, e-mail: [email protected]
