Project

General

Profile

Actions

Bug #1581

closed

mod_uploadprogress

Added by Anonymous about 15 years ago. Updated about 15 years ago.

Status:
Fixed
Priority:
Normal
Category:
documentation
Target version:
ASK QUESTIONS IN Forums:

Description

on r1992
mod_uploadprogress doesn't work correctly to me

checking at http://www.alaunt.com/server-config (uploadprogress correctly loaded)

then http://www.alaunt.com/progress (return 404??)

i have uploaded all the example (changed by needing) but query to progress return 404 page not found, even after upload start.

i have read the other ticket, and docs that report the change on post and get query, but progress page still return 404.

also please notice that on component isn't possible to choose mod_uploadprogress.

Actions #1

Updated by yelims about 15 years ago

Hi

read this ticket here http://trac.lighttpd.net/trac/ticket/1300

it seems like similar issue that i solved

im currently using lighttpd r2020 and above on production servers for a huge file hosting site (alexa ~700) with mod_uploadprogress working perfectly for huge file uploads

Actions #2

Updated by Anonymous about 15 years ago

i have already read the ticked, and this doesn't not help unfortunatly.

the situation seem to be different, on ticket you see that /progress actually reply, but mine is 404 error, not 400 ok + empty data.

Actions #3

Updated by Anonymous about 15 years ago

ok find a solution
seems that the default value doesn't work for me :S

$HTTPhost == "www.alaunt.com" {
server.document-root= "/home/rama/wwalaunt"
upload-progress.progress-url = "/progress" --> ADD THIS ONE
}

now work like a charm

Actions #4

Updated by stbuehler about 15 years ago

  • Status changed from New to Fixed
  • Resolution set to fixed

The documentation was wrong in saying that the progress-url is "/progress" by default; that is just the value which is used normally.

The default is empty, which means the modules is disabled.

Actions

Also available in: Atom