HttpMessageEncoder should add Header "Transfer-Encoding: chunked" if HttpMessage.isChunked()

[normanmaurer]

If HttpMessage.getChunked() is true, we should make sure we also add the "Transfer-Encoding: chunked" header to the message if its not already present. This should be what the user / dev does also expect here.

[normanmaurer]

@trustin As this is kind of not backward compatible, do we also want to have it in 3.3.x ?

[normanmaurer]

We should also adjust the javadocs in HttpMessage then...

[trustin]

It's an expected behavior. HttpMessageDecoder splits the content into multiple HttpChunks and calls setChunked(true) if the content length is large. It doesn't necessarily mean that the HTTP message's encoding is chunked. But yeah, it's better document this behavior more clearly.

[normanmaurer]

Thats true here.. but what about if you use it for HttpResponse's ? I think there it makes sense..

[trustin]

Oh I see. Then what about modifying HttpMessageEncoder so that it sets the Transfer-encoding header if HttpMessage.isChunked() is true (unless it's set already)?

[normanmaurer]

Yeah.. That will make most sense I guess... Let me do it and also make things more clear in the apidocs.

[normanmaurer]

Ok the HttpMessageEncoder does now add the header if its not present.