nginx_uploadprogress_module v0.2

Joerg Diekmann lists at
Tue Feb 5 15:14:14 MSK 2008

Does this work for Internet Explorer?

When I do this in my FF:

I get back - as expexted - the following plain text:

new Object({ 'state' : 'starting' })

But, if I do this in Internet Explorer:
I get back an error alert box saying:

Internet Explorer cannot download  .... 9d9c3264ccfabd2bce1aaf919cfbdd 
Internet Explorer was not able to open this Internet site. The requested 
site is either unavailable or cannot be found. Please try again later.

When I look into my nginx log files, I can see that the request returned 
a 200 status.

Any ideas. Any manual overrides I need to perform on IE so that it 


Brice Figureau wrote:
> On Thu, 2007-10-11 at 13:55 +0200, Otto Bretz wrote:
>> To try it out I used a copy of the lighttpd upload page[1]. Is that ok? 
>> I compiled the module with-debug as well and have attached the log of an 
>> upload attempt.
> The progress report handler doesn't yet support case-insentive progress
> id parameter (I know it sucks, but that's on my todo list for v0.3).
> Apply this patch to your upload.html (provided it is the same as the
> file on the webpage you referenced):
> --- upload.html.orig    2007-10-11 14:21:26.000000000 +0200
> +++ upload.html 2007-10-11 14:21:36.000000000 +0200
> @@ -40,7 +40,7 @@
>      if(!req) return;
>"GET", "/progress", 1);
> -    req.setRequestHeader("X-Progress-Id", uuid);
> +    req.setRequestHeader("X-Progress-ID", uuid);
>      req.onreadystatechange = function () {
>        if (!req) {
>          window.clearTimeout(interval);
> And then it will work fine.
> If you are testing locally (ie the server is on the same computer or LAN
> as the client), you won't see the progress bar evolving, because the
> bandwidth is too high.
> If you try on a distant server with limited bandwidth it works fine, the
> progress bar is slowly increasing.
> If you want to see the progress evolving on localhost, I suggest you
> reduce interval_msec in upload.html to something like 150 or 200,
> otherwise the first /progress probe is sent after the upload has
> finished :-)
> To test that the upload progress works fine, I'm using curl:
> To initiate the upload:
> curl -v -Ffilename=@file-to-upload --limit-rate 1k 
> "http://localhost/upload.html?X-Progress-ID=1234567890123456789019"
> And to see the probe in action:
> curl -v -H'X-Progress-ID: 1234567890123456789019' 
> "http://localhost/progress"
> If you want to send me debug material, please send them privately and
> not on the list, that might annoy people not interested in our
> discussion...
> Anyway, let me know if that's working for you, and do not hesitate to
> report any issues or improvements,

Posted via

More information about the nginx mailing list