Disabling chunked in nginx. What threatens?

Question

linux

What threatens chunked_transfer_encoding off in a certain location of nginx if it is planned to send a large amount of data to the server in response and what is the maximum amount of data nginx can accept?

Answer 1

What threatens chunked_transfer_encoding off?
This threatens to disable HTTP Keep-Alive in the absence of Content-Lenght.
What is the maximum amount of data nginx can accept?
This does not depend on the value of the directive chunked_transfer_encoding.
If we are talking about HTTP(S) buffering and proxying, then see the description of the directive proxy_buffering:
nginx.org/r/proxy_buffering/ru

Answer 2

From the wiki: Without a chunked transfer encoding mechanism, a Content-length header must be specified with each HTTP packet so that the client can find the end of the transmitted message.

Answer 3

chunked encoding is used to allow the server to respond in chunks. If it is disabled, then the server should save the response from the backend to a buffer in memory or on disk and return it in one piece. This is less beneficial in terms of performance.