[ 
https://issues.apache.org/jira/browse/HTTPCORE-333?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13573473#comment-13573473
 ] 

Anton Khitrenovich commented on HTTPCORE-333:
---------------------------------------------

I know that Commons-HttpClient 3.1 is obsolete and I realize that this issue 
will likely never be fixed there. Yet, it is still used in latest versions of 
many open source projects - for example, Axis2. The fact that there are no 
updates to 3.1 branch forces the developers that indirectly rely on Client 3.1 
to fork the code and fix such issues in private branches. I guess this is not 
the intention of the project owner, and I will be glad to get this patch as the 
official fix for Client 3.1. Thanks!
                
> ChunkedInputStream does not handle sockets with timeouts - Client 3.1
> ---------------------------------------------------------------------
>
>                 Key: HTTPCORE-333
>                 URL: https://issues.apache.org/jira/browse/HTTPCORE-333
>             Project: HttpComponents HttpCore
>          Issue Type: Bug
>            Reporter: Anton Khitrenovich
>            Priority: Minor
>         Attachments: HttpClient_829.java, 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.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to