[
https://issues.apache.org/jira/browse/HTTPCORE-219?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12841507#action_12841507
]
Oleg Kalnichevski commented on HTTPCORE-219:
--------------------------------------------
James, if you are talking about some _arbitrary_ _non-standard_ methods what is
the point of referring to the section of the specification that refers to the
_standard_ HTTP methods?
If the transport you are developing needs to support arbitrary non-standard
methods, just make those methods implement HttpEntityEnclodingRequest interface
and then let HttpCore generate an entity for those methods based on content of
Content-Length or Transfer-Encoding headers or leave it null if those headers
are not present. If you do not like this kind of approach, just implement a
custom message parser as described here [1] and do whatever your heart desires.
Oleg
[1
]http://hc.apache.org/httpcomponents-core/tutorial/html/advanced.html#d0e2470
> 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]
