[
https://issues.apache.org/jira/browse/HTTPCORE-736?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17702623#comment-17702623
]
Oleg Kalnichevski commented on HTTPCORE-736:
--------------------------------------------
[~reschke] And I am not surprised. I half expected you to post to this issue
and say exactly that. However, the sad truth is there is not a single blip in
RFC 2616 that it is valid for GET, HEAD, OPTIONS and DELETE methods to enclose
an entity. In fact It is actually crystal clear about only POST and PUT being
entity enclosing methods, which makes good sense. If the authors of the
specification had had something different in mind they have certainly failed to
have committed it in writing.
Oleg
> HttpClient GET method adds Content-Length: 0 header
> ---------------------------------------------------
>
> Key: HTTPCORE-736
> URL: https://issues.apache.org/jira/browse/HTTPCORE-736
> Project: HttpComponents HttpCore
> Issue Type: Bug
> Affects Versions: 4.4.16, 5.2.1
> Reporter: Jin Xu
> Priority: Critical
> Time Spent: 50m
> Remaining Estimate: 0h
>
> HttpClient GET method adds Content-Length: 0 header
> This would cuase some server/firewall deny this kind of http requests.
> See fixes of the same bug in other frameworks:
> java: https://bugs.openjdk.org/browse/JDK-8283544
> dart: https://github.com/dart-lang/shelf/pull/180
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@hc.apache.org
For additional commands, e-mail: dev-h...@hc.apache.org
