Bug #1457
closedmod_uploadprogress broken (404 on progress URL)
Description
It seems that mod_uploadprogress is (still?) broken in the 1.5 branch (tested with release 1.5.0-r1992).
Requesting the /progress URL simply returns a 404. It seems that http://upload.lighttpd.net/progress has the same problem...
Enabling debug shows:
mod_uploadprogress.c.450: (trace) (uploadprogress) urls /images/favicon.ico /progress
mod_uploadprogress.c.450: (trace) (uploadprogress) urls /progress /progress
In other words: it looks like the queried URL isn't correctly matched against the progress URL?
Updated by Anonymous about 17 years ago
Just checked out the latest trunk (revision 2025), and the problem also occurs there.
Updated by tx about 17 years ago
just put in configuration
upload-progress.progress-url = "/progress"
Updated by Anonymous about 17 years ago
Replying to tx:
just put in configuration
upload-progress.progress-url = "/progress"
Obviously I already tried tweaking these options, but without luck. It's a bug, as said earlier upload.lighttpd.net has the same problem.
Updated by yelims about 17 years ago
mod_uploadprogress is working fine (i have it on a production site with half million pagewviews a day) using r2025 here but anything above r1896 is fine
see my note at the end of
http://trac.lighttpd.net/trac/wiki/Docs%3AModUploadProgress
i also posted an example of a working upload progress
Updated by yelims about 17 years ago
also jan knows thats upload.lighttpd.net has the problem but he has not time to update it and his example
thats why i edited the wiki and added an updated example
this ticket should be closed
Updated by Anonymous about 17 years ago
I disagree here... I checked your example, but it doesn't fix the problem.
Here's a proof that the progress URL is indeed returning a 404 (generate a random 32-char number and query /progress):
$ curl -H "X-Progress-ID: $(echo $$ | md5sum | head -c32)" http://127.0.0.1/progress -v- About to connect() to 127.0.0.1 port 80 (#0)
- Trying 127.0.0.1... connected
- Connected to 127.0.0.1 (127.0.0.1) port 80 (#0)
GET /progress HTTP/1.1
User-Agent: curl/7.16.4 (i686-pc-linux-gnu) libcurl/7.16.4 OpenSSL/0.9.8d zlib/1.2.3
Host: 127.0.0.1
Accept: */*
X-Progress-ID: 195975ae1fcf143c620ebd0dc25ef325
< HTTP/1.1 404 Not Found
< Content-Type: text/html
< Content-Length: 345
< Date: Tue, 20 Nov 2007 22:56:23 GMT
< Server: lighttpd/1.5.0
Seems like a bug to me... or am I missing something?
Updated by Anonymous about 17 years ago
I just noticed that my upload-progress.progress-url = "/progress" key-value pair was inside a conditional ($HTTPhost =~ ...).
I'm very sorry... hopefully this ticket will serve its purpose for people with the same problem.
Thanks!
Updated by stbuehler over 16 years ago
- Status changed from New to Fixed
- Resolution set to invalid
Also available in: Atom