Content-Length and Transfer-Encoding headers in Spring MVC

Asked Oct 03 '17 at 09:32

Active Oct 03 '17 at 12:29

Viewed 2,028 times

I'm using Spring MVC and get Transfer-Encoding header in all responses. AFAIK it tells that the response is partial. But at the same time I get all the data, no problems at all. I've found that to disable Transfer-Encoding header generation Content-Length header should be added to response and ShallowEtagHeaderFilter filter can help with it. But this filter's purpose is different: to use ETags.

I would like to know is there any problem having Transfer-Encoding header? In which cases I can run into troubles? Is it considered as bad practice, if so why?

Thank you in advance very much!

edited Oct 03 '17 at 12:29

asked Oct 03 '17 at 09:32

Dmitry Senkovich

5,521
8
37
74

I assume you mean in *responses*? And what is the *value* of the header field? If it's "chunked", you may want to read . – Julian Reschke Oct 03 '17 at 12:19
1

@JulianReschke yes, it was a mistake, edited the question. Yes, the value is chunked. Ok, I will take a look, thank you! – Dmitry Senkovich Oct 03 '17 at 12:31

Content-Length and Transfer-Encoding headers in Spring MVC

0 Answers0