3 messages in ru.sysoev.nginxRe: Ebb and Transfer-Encoding: chunked
FromSent OnAttachments
John MillerNov 21, 2008 4:05 pm 
Dave CheneyNov 21, 2008 8:07 pm 
Maxim DouninNov 22, 2008 3:28 am 
Actions with this message:
Paste this link in email or IM:
Paste this link in email or IM:
Atom feed for this thread
Paste this URL into your reader:
Subject:Re: Ebb and Transfer-Encoding: chunkedActions...
From:Dave Cheney (da@cheney.net)
Date:Nov 21, 2008 8:07:25 pm
List:ru.sysoev.nginx

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