On Sun, Mar 15, 2015 at 06:54:09PM +0000, Artyom Beilis wrote:
> In any case FastCGI contains "end of data termination" and
> content length isn't required by HTTP, actually HTTP/1.1 supports
> chunked transfer encoding to eliminate need of content-lenght.
It is still helpful for clients if the server sends content-length, if
it is known at the beginning of the transfer. For HTTP/1.0, it is the
only way to support keep-alive and to reliably detect the end of
transmission. For HTTP/1.1, it reduces the overhead by avoiding chunked
transfer encoding. It also allows progress reports, something sadly too
many sites nowadays break even for static content. There are some broken
CDNs even. In short, if you know the size of the content, set
content-length.
But that's an unrelated topic, I still don't even understand OP's
original problem.
Joerg
|
