File uploads and client_body_temp_temp problems

Hi, I’m running nginx as a reverse proxy for an Apache/mod_perl
application, and have a fancy-upload progress bar that measures the
amount of content uploaded. If the script doesn’t see any progress
after several seconds, the client-side JavaScript assumes the upload
has failed for some reason and restarts the upload.

However, now that I have nginx running in front of Apache, it seems to
be buffering the uploaded content and isn’t sending any of it to
Apache until the upload finishes (or at least until the upload
progresses long enough for the client-side to give up and retry). Is
there any way I can tell nginx to stop buffering and simply send all
the content to Apache as it recieves it? I only am using nginx for
SSL and serving static files, so I don’t want it to do anything
special to my dynamic URIs.

Can anyone help me out with this, or tell me if there’s a way my
Apache application can detect the upload in-progress within nginx? As
long as I can watch the upload progress I can be happy, but my
application needs to be made aware of the upload.

Thank you

By default this is unfortunately impossible. It’s what forced me to move
away from nginx and I had to use pound as my main proxy.
Perhaps there is a third party module somewhere that does this.

Sergej

I find it hard to believe that, with all these sites working behind
nginx that there isn’t a better answer than “Switch web servers”.
There must be someone here doing file uploads, since it is a very
common webapp requirement.

Is there anything anyone has done to reduce the impact of this
problem? I already switched from lighttpd to nginx, and I really
don’t want to have to switch it for yet another “flavour of the month”
web server.

On Jul 29, 2008, at 10:37 AM, Michael Nachbaur wrote:

I find it hard to believe that, with all these sites working behind
nginx that there isn’t a better answer than “Switch web servers”.
There must be someone here doing file uploads, since it is a very
common webapp requirement.

Is there anything anyone has done to reduce the impact of this
problem? I already switched from lighttpd to nginx, and I really
don’t want to have to switch it for yet another “flavour of the
month” web server.

Unfortunately nginx always buffers file uploads and will not pass
them to the backend until after the upload is complete. There are two
modules that can mitigate this factor though that are worth checking
out. one of them parses the multipart body in nginx and places a file
on the filesystem your backend can get without parsing. The other one
does upload progress bars in nginx itself keeping the load and polling
off of your backends.

http://www.grid.net.ru/nginx/upload.en.html
http://wiki.codemongers.com/NginxHttpUploadProgressModule

'Cheers-
-Ezra

This forum is not affiliated to the Ruby language, Ruby on Rails framework, nor any Ruby applications discussed here.

| Privacy Policy | Terms of Service | Remote Ruby Jobs