[PATCH] disable chunked filter don't change keepalive
mdounin at mdounin.ru
Sun Jan 22 22:05:12 UTC 2012
On Sun, Jan 22, 2012 at 07:38:22PM -0200, Wandenberg Peixoto wrote:
> Ok. But with this I can't use any other way to do a chunked connection. Is
> mandatory to use chunked filter.
> I'm doing a chunked encoding connection, only don't want to use this filter
> as I said before.
> Has any other way to use chunked connections without use chunked filter?
There is no one supported. I would recommend using chunked filter
instead. Chunked encoding is a core part of http, and hence
chunked filter is essential part of nginx's http functionality.
Trying to replace it isn't supported and won't work well.
(And yes, I know the basic and I believe the only reason why you
are trying to avoid chunked filter: it used to consume memory for
long-lived connections. This is no longer true since nginx 1.1.4,
and I belive there is no real reason to avoid using it now.)
> Chunked filter could look to content-length instead only the enabled var?
> Or this be a responsible for header filter?
> On Sun, Jan 22, 2012 at 7:29 PM, Maxim Dounin <mdounin at mdounin.ru> wrote:
> > Hello!
> > On Sat, Jan 21, 2012 at 10:46:12PM -0200, Wandenberg Peixoto wrote:
> > > I don't know if there is some reason to disable keepalive if chunked
> > filter
> > > is disabled.
> > The reason is http protocol: to keep connections alive there
> > should be either content length known or chunked encoding used.
> > Maxim Dounin
> > _______________________________________________
> > nginx-devel mailing list
> > nginx-devel at nginx.org
> > http://mailman.nginx.org/mailman/listinfo/nginx-devel
> nginx-devel mailing list
> nginx-devel at nginx.org
More information about the nginx-devel