Allow configuration of whether HttpMessageConverters should set content-length header [SPR-8682]

[spring-projects-issues]

Bob Jacoby opened SPR-8682 and commented

I use spring with Apache's HttpClient 4.1. There is an outstanding feature request for officially supporting this version of HttpClient since the currently supported version (3.x) is no longer supported (see #11385). I created a port to the newer version of HttpClient (code included in referenced issue).

However, in 3.0.6 the HttpMessageConverters now set the content-length header on the message prior to using the httpclient to send the message. HttpClient 4.1 expects this header to NOT be set because it expects to be the one to set that header.

It would be nice to at least have the option for the converters to not set the content length. Ideally it would default to not setting them since that would be compatible with Spring 3.0.5. Otherwise I will have to rewrite all the message converters to upgrade to 3.0.6.

---

Affects: 3.0.6

Issue Links:

• Truncated HTTP responses [SPR-8867] #13509 Truncated HTTP responses

[spring-projects-issues]

Rossen Stoyanchev commented

HttpClient 4.1 expects this header to NOT be set because it expects to be the one to set that header

What is the behavior of HttpClient 4.1 you've observed when the Content-Length header is set?

[spring-projects-issues]

Rossen Stoyanchev commented

Also worth mentioning that we have integration tests for all the ClientHttpRequestFactories that operate against a Servlet. So a stack trace or an error message would help to understand what the exact problem is. Ideally report these against Spring 3.1 RC2 (just released). The final release might come in the next two weeks.