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

Maxim Valyanskiy edited comment on HTTPCORE-175 at 11/17/10 3:54 AM:
---------------------------------------------------------------------

Oleg, Is there any chance to get 3.1.1 with bugfix for this bug? We are using 
HttpClient 3 for HTTP-protocol compliance testing of our HTTP implementation. 
This bug can mask problems in our implementation

      was (Author: maxim.valyanskiy):
    Oleg, Is there any change to get 3.1.1 with bugfix for this bug? We are 
using HttpClient 3 for HTTP-protocol compliance testing of our HTTP 
implementation. This bug can mask problems in our implementation
  
> ChunkedInputStream Accepts Corrupted Chunked Input 
> ---------------------------------------------------
>
>                 Key: HTTPCORE-175
>                 URL: https://issues.apache.org/jira/browse/HTTPCORE-175
>             Project: HttpComponents HttpCore
>          Issue Type: Bug
>          Components: HttpCore
>    Affects Versions: 4.0-beta3
>         Environment: httpClient 3.1
>            Reporter: Mick Timony
>             Fix For: 4.0
>
>         Attachments: hc3x-truncated-chunks.patch, 
> httpcore-truncated-chunk.patch
>
>
> In one of our production environments we are seeing a random issue where 
> incomplete content is being received on a server which we have narrowed down 
> to httpClient's ChunkedInputStream. 
> If a corrupted and incomplete chunk is sent to httpClient it will be accepted 
> as the final chunk in the stream under the condition that the reported 
> chunk's size is greater than the actual size of the chunk.
> I will provide and example and associated unit test in comments below.

-- 
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]

Reply via email to