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

Oleg Kalnichevski commented on HTTPCORE-296:
--------------------------------------------

Curl also does not include 'Content-Length: 0' header if one does not specify 
any content to post. I think this is wrong, but I'll make sure HttpCore can 
handle such requests.

Oleg 
                
> IdentityDecoder fails to consume as POST request with Content-Length 0 (zero)
> -----------------------------------------------------------------------------
>
>                 Key: HTTPCORE-296
>                 URL: https://issues.apache.org/jira/browse/HTTPCORE-296
>             Project: HttpComponents HttpCore
>          Issue Type: Bug
>          Components: HttpCore NIO
>    Affects Versions: 4.2-alpha2
>            Reporter: Roland Hänel
>             Fix For: 4.2-beta2
>
>
> If a client submits a POST with Content-Length 0, the HttpCore framework will 
> fire the onContentReceived(...) method of the HttpAsyncRequestConsumer once. 
> However, the decoder (passed as an argument to onContentReceived()) will 
> never enter the "completed" state, because no bytes will actually be received 
> from the client. However, reaching the "completed" stage of the decoder is an 
> requirement for the HttpAsyncServiceHandler to finally process the request 
> (i.e., call the handle(...) method).
> This leads to the (incorrect) behavior that it is impossible to handle a POST 
> request with Content-Length 0 in HttpCore NIO.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
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