[
https://issues.apache.org/jira/browse/HTTPCLIENT-1124?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13100228#comment-13100228
]
Oleg Kalnichevski commented on HTTPCLIENT-1124:
-----------------------------------------------
@Jon,
Section 9.5 and 9.6 of RFC 2616 define POST and PUT as only methods expected to
enclose a content body and section 4.3 explicitly prohibits other request
methods from enclosing a content body. HttpClient is _fully_ HTTP spec
compliant in this regard, as long as RFC2616 is not superseded by a newer RFC.
There will always be people demanding changes in other peoples' code in order
to solve their immediate problem or fix their own leaking abstraction. That is
the way of open-source projects.
Oleg
> Can't send request body with HTTP methods other than POST and PUT
> -----------------------------------------------------------------
>
> Key: HTTPCLIENT-1124
> URL: https://issues.apache.org/jira/browse/HTTPCLIENT-1124
> Project: HttpComponents HttpClient
> Issue Type: Bug
> Components: HttpClient
> Affects Versions: 4.1.2
> Reporter: Alexey Levan
> Priority: Minor
>
> I'd like to have a possibility to send an HttpEntity regardless of method of
> request. The HTTP spec doesn't prohibit that (AFAIK, even GET requests with
> body are allowed), and any spec-compliant implementation shouldn't do it
> either. I suggest merging HttpEntityEnclosingRequestBase with
> HttpRequestBase, since there's really no reason to make this artifical
> restriction.
--
This message is automatically generated by JIRA.
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]
