On Fri, Feb 25, 2011 at 9:56 AM, Valery Kholodkov
<valery+nginxen@grid.net.ru> wrote:
> Web George wrote:
>>
>> thanks for your info.
>>
>> Can NGINX bypass and sent it directly to backend ?
>
> It can, but without streaming (with buffering), which is now what you want
> as we have already figured out.
>
>>
>> thanks
>> George
>>
>> 2011/2/25 Valery Kholodkov <valery+nginxen@grid.net.ru
>> <mailto:valery%2Bnginxen@grid.net.ru>>
>>
>>
>> ----- Valery Kholodkov <valery+nginxen@grid.net.ru
>> <mailto:valery%2Bnginxen@grid.net.ru>> wrote:
>> >
>> > ----- Web George <webgreatwall@gmail.com
>> <mailto:webgreatwall@gmail.com>> wrote:
>> > > Thanks Weibin's feedback.
>> > >
>> > > I searched a mail with the same issue.
>> > > ref: http://forum.nginx.org/read.php?2,5506,146254
>> > >
>> > > >From the update of Igor, it should be an issue and would be
>> developed.
>> > >
>> > > We do not know the latest status...
>> > >
>> > > It seems that UPLOAD module can not solve the issue.
>> >
>> > No, it doesn't seem so. upload module is especially designed for
>> solving this issue.
>>
>> Correction: yes, you are right and I am wrong, as long as you are
>> talking about streaming uploads to the backend.
>>
>> However, if you want to stream the entire request body without
>> modifications, why don't you make clients send requests directly to
>> the backend?
>>
>> --
>> Regards,
>> Valery Kholodkov
>>
>> _______________________________________________
>> nginx mailing list
>> nginx@nginx.org <mailto:nginx@nginx.org>
>> http://nginx.org/mailman/listinfo/nginx
When I've run into this type of issue, usually it's due to the backend
(Apache in my case) not seeing any activity over the connection that
nginx has made with it, while nginx is buffering the upload to a temp
file. In that case, it was just a matter of upping Apache's timeout.
_______________________________________________
nginx mailing list
nginx@nginx.org
http://nginx.org/mailman/listinfo/nginx
