[
https://issues.apache.org/jira/browse/HTTPCLIENT-1828?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15893824#comment-15893824
]
Julian Reschke commented on HTTPCLIENT-1828:
--------------------------------------------
RFC 2616 is indeed very unclear in that in one place it asks for the method
definition to "allow" something, and then not using that term at all in the
method definitions.
RFC 7230 improves this by clarifying the mechanism to determine the message
length, see change note:
"The algorithm for determining the message body length has been clarified to
indicate all of the special cases (e.g., driven by methods or status codes)
that affect it, and that new protocol elements cannot define such special
cases. CONNECT is a new, special case in determining message body length.
"multipart/byteranges" is no longer a way of determining message body length
detection. (Section 3.3.3)"
-- <https://greenbytes.de/tech/webdav/rfc7230.html#rfc.section.A.2.p.11>
That doesn't make it a different protocol, it's still HTTP/1.1.
> HttpDelete does not extend HttpEntityEnclosingRequestBase
> ---------------------------------------------------------
>
> Key: HTTPCLIENT-1828
> URL: https://issues.apache.org/jira/browse/HTTPCLIENT-1828
> Project: HttpComponents HttpClient
> Issue Type: Improvement
> Affects Versions: 4.5.1, 4.5.2, 4.5.3
> Reporter: Saravanakumar Selvaraj
> Fix For: 5.0 Alpha1
>
>
> Sending body in DELETE is allowed as the HTTP 1.1 specification does not
> forbid. Hence HttpDelete.class should extend from
> HttpEntityEnclosingRequestBase instead of HttpRequestBase.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@hc.apache.org
For additional commands, e-mail: dev-h...@hc.apache.org
