Question

Is it possible to set the content-length header and also use chunked transfer encoding? and does doing so solve the problem of not knowing the length of the response at the client side when using chunked?

the scenario I’m thinking about is when you have a large file to transfer and there’s no problem in determining its size, but it’s too large to be buffered completely.
(If you’re not using chunked, then the whole response must get buffered first? Right??)

thanks.

Answer 1

1. No:

"Messages MUST NOT include both a Content-Length header field and a non-identity transfer-coding. If the message does include a non-identity transfer-coding, the Content-Length MUST be ignored." (RFC 2616, Section 4.4)

2. And no, you can use Content-Length and stream; the protocol doesn’t constrain how your implementation works.