Opened 13 years ago

Closed 6 years ago

#6483 closed Feature request (invalid)

Ability to perform local verification of uploaded/downloaded files, with optional delete.

Reported by: Qriist Owned by:
Priority: normal Component: FileZilla Client
Keywords: Cc:
Component version: Operating system type:
Operating system version: Windows 7 Ultimate x64 / Ubuntu Jaunty x86

Description (last modified by Tim Kosse)


I'd love to use FileZilla as a permanent FTP solution, but to do this I need one feature that I think would be fairly easy to implement - though I have not looked at your source code.

Essentially, I would like your program, FileZilla, to have the ability to follow these steps, with appropriate preconfiguration as needed:

1: Uploads or downloads a file as normal.
2a: If server hashing is supported, simply hash compares with (any / best) hash algorithm available.
2b: If server hashing is NOT supported, (re)downloads the file at hand into a temp file and does a local binary compare.
3a: If the process from 2a or 2b fails it deletes the temp files and the appropriate local/remote file and starts with step 1 on the same file.
3b: If the process from 2a or 2b is successful it flags that operation as a success and continues.
4: Based on an optional per-queue setting it deletes the local or remote file that was just successfully transfered.
5: FileZilla continues with the next item and starts the process at step 1.

Essentially, I want a file-comparison while-loop. It really isn't as complicated as it sounds, and a somewhat minimal/gimped version of this has been made by myself (with help) in the BASH language utilizing cURL. I do great things with scripts (Windows side...!); but for things like this an already built GUI is amazing.

Fantastic work on FileZilla, by the way.

Following is a link to my BASH version, which is upload only and does not do server-side hashing at all... Nevertheless it will provide a solid foundation for you to check and examine the steps I desire. Thank you!

Change History (2)

comment:1 by Qriist, 13 years ago

Priority: highcritical

comment:2 by Tim Kosse, 6 years ago

Description: modified (diff)
Priority: criticalnormal
Resolution: invalid
Status: newclosed
Note: See TracTickets for help on using tickets.