Lighttpd

Just checked out the latest trunk (revision 2025), and the problem also occurs there.

just put in configuration
upload-progress.progress-url = "/progress"

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.

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

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

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):

• 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?

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!