Do we let Nginx to handle response Transfer-Encoding?

Iñaki Baz Castillo ibc at
Mon Dec 28 05:23:50 EST 2009

El Lunes, 28 de Diciembre de 2009, Eric Wong escribió:
> Iñaki Baz Castillo <ibc at> wrote:
> > Hi, I've checked that in case my Rack application (under Unicorn) doesn't
> > set "Content-Lentgh" neither "Transfer-Encoding", then Nginx
> > automatically adds "Transfer-Encoding: chunked" to the response (and
> > edits the body properly to be in chunked format).
> >
> > However Unicorn is sending a response with body but without
> > "Content-Lentgh" or "Transfer-Encoding", so IMHO it's incorrect according
> > to RFC 2616.
> >
> > So, should my Rack application handle this stuff? or is it better if I
> > let Nginx "fixing" it for me?
> Just load the Rack::ContentLength middleware, if you're building a Rack
> app from scratch.  Some frameworks already handle Content-Length for
> you.

The fact is that to realizing about the above, I already added Content-Length 
by myself in the Rck application :)


Iñaki Baz Castillo <ibc at>

More information about the mongrel-unicorn mailing list