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