[ 
https://issues.apache.org/jira/browse/HTTPCORE-736?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17702494#comment-17702494
 ] 

Oleg Kalnichevski commented on HTTPCORE-736:
--------------------------------------------

[~XenoAmess] I personally think that GET, HEAD, DELETE and OPTIONS with an 
enclosed entity are _idiotic_ and should have never been allowed. Unfortunately 
RFC 7230 made it legal for those methods to enclose an entity and therefore the 
request below is perfectly valid and HTTP/1.1 compliant proxies and servers 
must be able to handle it
{noformat}
HTTP/1.1 GET /
Content-Length: 0
{noformat}

Oleg

PS: Go easy on the kid. Every day at work I am seeing worse things done by 50+ 
senior developers
 

> 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

Reply via email to