[HTTPCORE-296] Server HTTP connections incorrectly handle entity enclosing requests containing neither Content-Length nor Transfer-Encoding headers

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 4.2-alpha2
• Fix Version/s: 4.2
• Component/s: HttpCore NIO
• Assignee: Unassigned
• Reporter: Roland Hänel
• Created: 12/Mar/12 16:51
• Updated: 05/Oct/13 20:09
• Resolved: 18/Mar/12 15:55

Description

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.