upload issue when NGINX actes as reverse proxy

[Mark Moseley]

On Sun, Feb 27, 2011 at 8:30 AM, Web George <webgreatwall at gmail.com> wrote:
> Do you mean that it is the configuration issue because of backend server ?
> I set the "buffing off".
>
>
> 2011/2/25 Mark Moseley <moseleymark at gmail.com>
>>
>> On Fri, Feb 25, 2011 at 9:56 AM, Valery Kholodkov
>> <valery+nginxen at 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 at grid.net.ru
>> >> <mailto:valery%2Bnginxen at grid.net.ru>>
>> >>
>> >>
>> >>    ----- Valery Kholodkov <valery+nginxen at grid.net.ru
>> >>    <mailto:valery%2Bnginxen at grid.net.ru>> wrote:
>> >>     >
>> >>     > ----- Web George <webgreatwall at gmail.com
>> >>    <mailto:webgreatwall at 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 at nginx.org <mailto:nginx at 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.

In my case, yes. I usually have the upload buffer set to a couple
hundred meg and slower clients wouldn't hit either the end of the
upload or the buffer limit before Apache had timed out the connection
from nginx. If you're not buffering though, then probably not relevant
to your issue.