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

[li zJay]

Hello!

@yaoweibin

> If you are eager for this feature, you could try my patch:
> https://github.com/taobao/tengine/pull/91. This patch has been running in
> our production servers.

what's the nginx version your patch based on?

Thanks!

On Fri, Jan 11, 2013 at 5:17 PM, 姚伟斌 <yaoweibin at gmail.com> wrote:

> I know nginx team are working on it. You can wait for it.
>
> If you are eager for this feature, you could try my patch:
> https://github.com/taobao/tengine/pull/91. This patch has been running in
> our production servers.
>
> 2013/1/11 li zJay <zjay1987 at gmail.com>
>
>> Hello!
>>
>> is it possible that nginx will not buffer the client body before handle
>> the request to upstream?
>>
>> we want to use nginx as a reverse proxy to upload very very big file to
>> the upstream, but the default behavior of nginx is to save the whole
>> request to the local disk first before handle it to the upstream, which
>> make the upstream impossible to process the file on the fly when the file
>> is uploading, results in much high request latency and server-side resource
>> consumption.
>>
>> Thanks!
>>
>> _______________________________________________
>> nginx mailing list
>> nginx at nginx.org
>> http://mailman.nginx.org/mailman/listinfo/nginx
>>
>
>
>
> --
> Weibin Yao
> Developer @ Server Platform Team of Taobao
>
> _______________________________________________
> nginx mailing list
> nginx at nginx.org
> http://mailman.nginx.org/mailman/listinfo/nginx
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.nginx.org/pipermail/nginx/attachments/20130113/94a31e3c/attachment.html>