Ebb and Transfer-Encoding: chunked

[Dave Cheney]

On 22/11/2008, at 11:06 AM, John Miller wrote:

> When and array (or something more complex) is passed
> to Ebb as the body, it sets 'Transfer-Encoding: chunked' and then  
> sends
> each yielded value as a chuck.
>
> NginX speaks to its back end services using HTTP/1.0 which does not
> include Transfer-Encoding.  It therefore adds it's own transfer  
> encoding
> and life becomes very messy.

If are responding to a HTTP/1.0 request you mustn't use Transfer- 
Encoding. The proper way to send a dynamic sized body to a HTTP/1.0  
upstream client is to give no Content-Length header then close the  
connection after sending the body. This sounds like Ebb is not doing  
the right thing, not nginx.

Cheers

Dave