Flength File Help “Failed To Find Flength File”

Flength File Help “Failed To Find Flength File”

Assuming the script is set up properly, you are probably dealing with some kind of write-caching. Some servers perform write-caching which prevents writing out the flength file or the entire CGITemp file during the upload. The flength file or the CGITemp file do not actually hit the disk until the upload is complete, making it worthless for reporting on progress during the upload. This may be fixed using a .htaccess file assuming your host supports them. Here is a link to an excellent tutorial on using .htaccess files. I strongly recommend giving it a quick read before attempting to install your own .htaccess file.


1. A mod_security module for Apache.

To fix it just create a file called .htaccess (that’s a period followed by “htaccess”) and put the following lines in that file. Upload the file into the directory where the Uber-Uploader CGI “.pl” scripts resides, or in some directory above it (like your server’s DOCUMENT_ROOT, i.e. the top-level of your webspace). htaccess files must be uploaded as ASCII mode, not BINARY. You may need to CHMOD the htaccess file to 644 or (RW-R–R–).

# Turn off mod_security filtering.
SecFilterEngine Off

# The below probably isn’t needed,
# but better safe than sorry.
SecFilterScanPOST Off

If the above method does not work, try putting the following lines into the file

SetEnvIfNoCase Content-Type \
“^multipart/form-data;” “MODSEC_NOPOSTBUFFERING=Do not buffer file uploads”

mod_gzip_on No

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.

Comments are closed.