[
https://issues.apache.org/jira/browse/HTTPCORE-219?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12841497#action_12841497
]
James Leigh commented on HTTPCORE-219:
--------------------------------------
The issue I want to raise is not about methods that do not allow sending an
entity-body, but rather methods that are either not known or permit an optional
message body. In these cases the "presence of a message-body in a request is
signaled by the inclusion of a Content-Length or Transfer-Encoding header field
in the request's message-headers". However, the HttpRequestFactory is not
provided with these header when the HttpRequest object is created preventing
httpCore from being reasonable used in theses cases.
> HttpRequestParser Fails to Detect Requests Without a Message Body
> -----------------------------------------------------------------
>
> Key: HTTPCORE-219
> URL: https://issues.apache.org/jira/browse/HTTPCORE-219
> Project: HttpComponents HttpCore
> Issue Type: Bug
> Components: HttpCore NIO
> Affects Versions: 4.0.1
> Reporter: James Leigh
>
> The HttpRequestParser uses the request method to determine if the request has
> a message body. However, HTTP 1.1 states that the presence of a message-body
> in a request is signaled by the inclusion of a Content-Length or
> Transfer-Encoding header field in the request's header fields. The parser
> should be changed to use the header to determine if a message body is present.
> As is a POST or PUT request is received without a message body cannot be
> processed. Furthermore, a GET request with a message body cannot be processed
> either.
--
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]
