Bug #1748
closedFalse information submitted from mod_uploadprogress
Description
When we use the mod_uploadprogress module to get the size of the current uploads we have a problem retrieving the correct information.
First we limited our upload to 100kb to have chunks submitted to the upload location. Then we start uploading files (through flash). As soon as flash reports that the upload is finished the next one is send. It seems that the server is not yet done with the first upload when the second one starts.
In most cases the progress information regarding the first upload are ok but those from the second one are broken.
Traces:
First error:
first file upload (worked):
mod_uploadprogress.c.508: (trace) connection is known: 24c1cf72b8caf62a942317d8252969b6, sending: new Object({ 'state' : 'uploading','received' : 3004744, 'size' : 3158006})
second file upload (the following message is send every second)
mod_uploadprogress.c.508: (trace) connection is known:
550ec14629b583aaf66a52ba43d9a7d2, sending: new Object({ 'state' : 'uploading','received' : 65536, 'size' : 2824965})
the second file upload seems to be stalled at 65536 bytes, but the file get submitted in full size.
Sometimes the error looks like this:
mod_uploadprogress.c.508: (trace) connection is known:
6606bd07d9ce9cbbf688fb51a91e6849, sending: new Object({ 'state' : 'uploading','received' : 0, 'size' : 0})
Again the file get submitted but we are not getting the right size and bytes_in
-- Simon.Schaefer
Updated by Anonymous over 16 years ago
I forgot to mention that we tested this with lighttp-1.5.0-r1992 and lighttpd-1.5.0-r2282 (current version at submission date)
-- Simon.Schaefer
Updated by stbuehler about 16 years ago
- Category changed from core to mod_uploadprogress
Updated by gstrauss over 8 years ago
- Description updated (diff)
- Missing in 1.5.x set to Yes
Also available in: Atom