Custom Query (8025 matches)

when i open p2p software and use filezilla client to upload a 300MB video file. After upload 100% complete, the video can't view correct on the ftp server. Maybe 50%(30min) or 70%(40min).

When uploading a file using FileZilla in my intranet from Win2k to IBM AIX, it takes about 2 minutes to upload a 8MB file. Achieving a 79KB/s throughput.

When using ftp in the MSDOS command prompt, it takes about 3 seconds. However, download files in the same environment only takes about 3 seconds. Upload from Win2k to Win2k machines took 30 seconds with FileZilla while ftp from command prompt took 3 seconds. There is no speed limit set.

Many sites use PHP or other scripting languages. Those scripts cannot be accessed by visitors of the site until they are fully uploaded to the server. During upload and until they are fully uploaded, they produce a 500 internal server error message (or white page, depending on the server configuration).

This is especially relevant when uploading and overwriting a large PHP file on the server, for example "functions.php", which disables the entire site during the upload, and can lead to unexpected results and even lost data in certain cases, for example when a visitor just submits a form.

My suggestion is to upload the file using a temporary name (instead of overwriting), and when the upload completes, rename back to the original name. On linux renaming over an existing FTP file is possible, but on Windows (or SFTP) it is not. So if the renaming fails, it should delete the original file, and then rename again. The downtime would still be much faster than with normal overwriting of the file.