Is it possible that nginx will not buffer the client body?

[Weibin Yao]

2013/3/14 Pasi Kärkkäinen <pasik at iki.fi>

> On Thu, Feb 28, 2013 at 10:12:47PM +0400, Maxim Dounin wrote:
> > Hello!
> >
>
> Hello,
>
> > On Thu, Feb 28, 2013 at 05:36:23PM +0000, André Cruz wrote:
> >
> > > I'm also very interested in being able to configure nginx to NOT
> > > proxy the entire request.
> > >
> > > Regarding this patch,
> > > https://github.com/alibaba/tengine/pull/91, is anything
> > > fundamentally wrong with it? I don't understand Chinese so I'm
> > > at a loss here...
> >
> > As a non-default mode of operation the aproach taken is likely
> > good enough (not looked into details), but the patch won't work
> > with current nginx versions - at least it needs (likely major)
> > adjustments to cope with changes introduced during work on chunked
> > request body support as available in nginx 1.3.9+.
> >
>
> Weibin: Have you thought of upstreaming the no_buffer patch to nginx 1.3.x
> so it could become part of next nginx stable version 1.4 ?
>
You can see my first email in this thread,  The nginx team are working on
it. But I don't know when they finish it. You can wait for their version.

Thanks.

>
> It'd be really nice to have the no_buffer functionality in stock nginx!
> (the current no_buffer_v5.patch seems to work OK for me on nginx 1.2.7)
>
> -- Pasi
>
> > --
> > Maxim Dounin
> > http://nginx.org/en/donation.html
> >
>
> _______________________________________________
> nginx mailing list
> nginx at nginx.org
> http://mailman.nginx.org/mailman/listinfo/nginx
>



-- 
Weibin Yao
Developer @ Server Platform Team of Taobao
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.nginx.org/pipermail/nginx/attachments/20130318/c4c5f18b/attachment.html>