Opened 3 years ago
Closed 3 years ago
#12674 closed Bug report (worksforme)
FileZilla Time Stamp is Incomplete
| Reported by: | Michael French | Owned by: | |
|---|---|---|---|
| Priority: | normal | Component: | FileZilla Client |
| Keywords: | Cc: | Michael French | |
| Component version: | 3.58.0 | Operating system type: | Windows |
| Operating system version: | 10 Pro |
Description
FileZilla is a very efficient file mover. However, there is a problem of time stamp marking where the moved file has the "modified" date as the current date instead of the original "modified" date of the file being moved. This problem occurs with the FileZilla menu selection "Preserve timestamps of transferred files" activated.
For reference, the Windows 10 copy and robocopy utilities preserve both the "modified" and "created" dates.
This FileZilla operation causes my backup operations using robocopy to needlessly copy files that are already up-to-date.
I've attached three file properties screen shots - 1) the original file; 2) the FileZilla upload; and 3) the robocopy upload. Notice the time stamps of the original and robocopy file are identical while the FileZilla file has a different "Created" date
Attachments (3)
Change History (4)
by , 3 years ago
| Attachment: | Original.jpg added |
|---|
by , 3 years ago
| Attachment: | FileZilla_upload.jpg added |
|---|
FileZilla uploaded file with preserve timestamps set
comment:1 by , 3 years ago
| Resolution: | → worksforme |
|---|---|
| Status: | new → closed |
Looking at FileZilla_upload.jpg the modification time is preserved correctly.
Other timestamps cannot be preserved as they have unclear semantics or aren't supported on other platforms.
Original file to be moved