yabsoft
08-02-2006, 04:20 PM
Assuming the script is set up properly, you are probably dealing with some kind of write-caching. Some servers perform write-caching which prevents getting the uploaded size of uploading files during the upload. there are two types of caching have been reported by users.
1. Mod_security module for Apache.
To fix it just create a file called .htaccess (that's a period followed by "htaccess") either in the root directory. Then put these lines into that file(if the .htaccess exists,append the below lines into that file):
<IfModule mod_security.c>
# Turn off mod_security filtering.
SecFilterEngine Off
# The below probably isn't needed,
# but better safe than sorry.
SecFilterScanPOST Off
</IfModule>
If this does not work, try putting these lines into the file
<IfModule mod_security.c>
SetEnvIfNoCase Content-Type \
"^multipart/form-data;" "MODSEC_NOPOSTBUFFERING=Do not buffer file uploads"
</IfModule>
2. "Performance Cache" enabled on OS X SERVER.
If you're running OS X Server and the progress bar isn't working, it could be because of "performance caching." Apparently if ANY of your hosted sites are using performance caching, then by default, all sites (domains) will attempt to. The fix then is to disable the performance cache on all hosted sites.
1. Mod_security module for Apache.
To fix it just create a file called .htaccess (that's a period followed by "htaccess") either in the root directory. Then put these lines into that file(if the .htaccess exists,append the below lines into that file):
<IfModule mod_security.c>
# Turn off mod_security filtering.
SecFilterEngine Off
# The below probably isn't needed,
# but better safe than sorry.
SecFilterScanPOST Off
</IfModule>
If this does not work, try putting these lines into the file
<IfModule mod_security.c>
SetEnvIfNoCase Content-Type \
"^multipart/form-data;" "MODSEC_NOPOSTBUFFERING=Do not buffer file uploads"
</IfModule>
2. "Performance Cache" enabled on OS X SERVER.
If you're running OS X Server and the progress bar isn't working, it could be because of "performance caching." Apparently if ANY of your hosted sites are using performance caching, then by default, all sites (domains) will attempt to. The fix then is to disable the performance cache on all hosted sites.