Filesize issue with Nginx Upload Progress Module

Server NGINX
1

Hi all,

we are using nginx in front of a mongrel cluster to serve our Rails
application.

I am now trying to run a Rails Metal in front of the Rails stack to
handle file uploads. Some of the files are then transferred to a ftp
server.

To give feedback to the uploader I have recompiled the nginx package to
include the Upload Progress Module.

The config file basically looks like the one in the UploadProgressModule
example:
http://wiki.nginx.org/NginxHttpUploadProgressModule#Configuration_Example

upload_progress uploadtracker 1m;

location /customer/files/ftp_upload {

mongrel on development mode runns on port 3001

proxy_pass http://127.0.0.1:3001;

track_uploads uploadtracker 30s;

}

location ^~ /upload_progress {
report_uploads uploadtracker;
}

location / {

standard config…

}

While uploading files, the server responds to the progress requests, but
the received data seems to be off. The file size is correct, but the
received part of the JSON is always equal to the size, no matter how
large the file is.

The Server response always looks something like this (in this case about
230kb file):

new Object({ ‘state’ : ‘uploading’, ‘received’ : 235134, ‘size’ : 235134
})

Can anybody help me resolve this problem, why the progress module does
not send the correct received size?

Thanks
MSc

Posted at Nginx Forum:

2

On 10/02/10 21:40, MSc wrote:

The Server response always looks something like this (in this case about 230kb file):

new Object({ ‘state’ : ‘uploading’, ‘received’ : 235134, ‘size’ : 235134 })

Can anybody help me resolve this problem, why the progress module does not send the correct received size?

What are the values of the various proxy_ settings?

This is not normal. Please compile nginx with --with-debug, activate the
error log in debug mode, then try to upload a file and finally create an
issue here, containing the nginx version, the upload progress version
and all other information that would make sense:

And send me privately the full compressed debug log, I will analyze it
to see what the issue can be.

Brice F.
My Blog: http://www.masterzen.fr/