[
https://issues.apache.org/jira/browse/HTTPCORE-219?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Oleg Kalnichevski resolved HTTPCORE-219.
----------------------------------------
Resolution: Invalid
I am sorry, James, but your assertion is incorrect. The decision as to whether
a message is entity closing or not is taken by HttpRequestFactory, not
HttpRequestParser. The default implementation of HttpRequestFactory can be
replaced by a custom impl, which can make all requests entity enclosing, if
you are absolutely sure you need to bastardize the HTTP protocol.
And no, GET requests MAY NOT have a content body. Only POST and PUT messages
are defined as entity enclosing by the RFC2616
Oleg
> 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]
