Forum: NGINX Upload module & Upload progress module do not work together

Announcement (2017-05-07): www.ruby-forum.com is now read-only since I unfortunately do not have the time to support and maintain the forum any more. Please see rubyonrails.org/community and ruby-lang.org/en/community for other Rails- und Ruby-related community platforms.
65ffc40cdcdfbb217083167167b384e5?d=identicon&s=25 unknown (Guest)
on 2008-11-06 12:35
(Received via mailing list)
Hi,

I would like to use the upload module and the upload progress module at
the
same time. Unfortunately, the upload progress module can only work with
proxy_pass and fastcgi, however, not with upload_pass.

Is there a way to use both modules at the same time ?

Kind regards,
Markus
Abbd9d5312c5d54114a96a35dc94fdb1?d=identicon&s=25 Valery Kholodkov (Guest)
on 2008-11-06 14:25
(Received via mailing list)
Attachment: nginx.conf (768 Bytes)
> I would like to use the upload module and the upload progress module at
> the
> same time. Unfortunately, the upload progress module can only work with
> proxy_pass and fastcgi, however, not with upload_pass.
>
> Is there a way to use both modules at the same time ?

Upload module is known to work with upload progress module. Please see
attached example configuration, it is known to work on my friend's
server.
Feel free to complain anyway.
65ffc40cdcdfbb217083167167b384e5?d=identicon&s=25 Markus (Guest)
on 2008-11-06 19:40
(Received via mailing list)
Thanks for your help. Now it works great !

Kind regards,
Markus

Valery Kholodkov schrieb:
2f21e66562660144e16da0456a9210e5?d=identicon&s=25 Brice Figureau (Guest)
on 2008-11-07 18:14
(Received via mailing list)
On Thu, 2008-11-06 at 14:18 +0100, Valery Kholodkov wrote:
> > I would like to use the upload module and the upload progress module at
> > the
> > same time. Unfortunately, the upload progress module can only work with
> > proxy_pass and fastcgi, however, not with upload_pass.
> >
> > Is there a way to use both modules at the same time ?
>
> Upload module is known to work with upload progress module. Please see
> attached example configuration, it is known to work on my friend's server.
> Feel free to complain anyway.

I never tried it myself, but one user was reporting that sometimes the
progress modules reports incorrect results toward the end of the upload.
I tried to fix it on my side but I didn't had much time to do so.

Maybe the configuration you gave overcome this issue?
If it does, then I'll add it to the progress module example as
reference, if you do agree.

Also, I wondered (although I don't really have the development bandwidth
nowadays), if we could find a way to have the progress module using
hooks in the upload module to report the right upload progress instead
of the crude and fragile hack I adopted for the regular nginx.

Thanks,
Abbd9d5312c5d54114a96a35dc94fdb1?d=identicon&s=25 Valery Kholodkov (Guest)
on 2008-11-08 17:43
(Received via mailing list)
Brice Figureau <brice+nginx@daysofwonder.com> wrote:

> If it does, then I'll add it to the progress module example as
> reference, if you do agree.

No it doesn't. The problem you described most likely happens because
client request body carrying files contains encapsulation as well as
form
fields. This inflates request body up to certain amount.

> Also, I wondered (although I don't really have the development bandwidth
> nowadays), if we could find a way to have the progress module using
> hooks in the upload module to report the right upload progress instead
> of the crude and fragile hack I adopted for the regular nginx.

In fact upload module is a small hack as well.

But you can take a look at (not officially published yet) branch 2.1 of
upload module and see how discarding and unzip modules are implemented:

http://grid.net.ru/nginx/download/nginx_upload_mod...

Although filters in this branch of upload module are not chainable yet,
I
plan to implement it. And if you make any filter based on current
implementation in between, it will be very easy to integrate such
additional filter.
This topic is locked and can not be replied to.