mod_uploadprogress broken (404 on progress URL)
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 yelims over 13 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
i also posted an example of a working upload progress
Updated by Anonymous over 13 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
< 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?
Also available in: Atom