Transfer-Encoding: chunked
Transfer-Encoding: chunked isn’t needed for progressive rendering. However, it is needed when the total content length is unknown before the first bytes are sent.
Transfer-Encoding: chunked isn’t needed for progressive rendering. However, it is needed when the total content length is unknown before the first bytes are sent.
The correct usage, as defined in RFC 2616 and actually implemented in the wild, is for the client to send an Accept-Encoding request header (the client may specify multiple encodings). The server may then, and only then, encode the response according to the client’s supported encodings (if the file data is not already stored in … Read more