[
https://issues.apache.org/jira/browse/HTTPCORE-643?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17169564#comment-17169564
]
Carter Kozak commented on HTTPCORE-643:
---------------------------------------
You are correct. I agree that this should be configurable, based on the RFC it
should probably be enabled by default.
I'm not certain whether core was the right place to file this ticket. Depending
on how the configuration fits together the client module might make sense, or a
combination of the two.
> Add zero content-length to PUT and POST requests with no entity
> ---------------------------------------------------------------
>
> Key: HTTPCORE-643
> URL: https://issues.apache.org/jira/browse/HTTPCORE-643
> Project: HttpComponents HttpCore
> Issue Type: Improvement
> Affects Versions: 5.0.1
> Reporter: Carter Kozak
> Priority: Major
>
> [https://tools.ietf.org/html/rfc7230#section-3.3.2] states "A user agent
> SHOULD send a Content-Length in a request message when
> no Transfer-Encoding is sent and the request method defines a meaning
> for an enclosed payload body."
>
> I encountered a proxy that rejected both PUT and POST requests with no
> content-length and no body by returning a 411 "Length Required" status. I
> believe this is rare, and servers are expected to support requests with and
> without a defined content length and no body, but it would be helpful to add
> the content-length by default to avoid incompatibility.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
