Opened 4 years ago

Closed 4 years ago

Last modified 4 years ago

#10784 closed Bug report (rejected)

FileZilla Client 3.16.0 not preserving timestamps on upload

Reported by: Seagram Owned by:
Priority: high Component: FileZilla Client
Keywords: timestamp preservation Cc:
Component version: 3.16.0 Operating system type: Windows
Operating system version: 7 64 bits

Description

Hello,

Using FZ for years, to manage web sites on hosted servers.
With proper settings, FZ always preserved timestamps on upload as expected.

Each time FZ proposes to update, I do it. Currently I am on version 3.16.0 (last one).
Today I do major updates and detects that timestamps on hosted server are NOT preserved. I have checked that setting IS active (see capture).

Of course, I can not control whether some change on hosted server is the origin of the issue.

What can I do for further investigation?
I have activated log, but no data yet, I have to do some more uploads ...

Attachments (2)

2016-03-13_FileZilla_Client_Environment.txt (653 bytes) - added by Seagram 4 years ago.
Filezilla Client 3.16.0 environment
2016-03-13_15-56-05 FZ-3-16-0 timestamp issue.png (157.7 KB) - added by Seagram 4 years ago.
FileZilla GUI (french) with clues about timestamps not preserved

Download all attachments as: .zip

Change History (5)

Changed 4 years ago by Seagram

Filezilla Client 3.16.0 environment

Changed 4 years ago by Seagram

FileZilla GUI (french) with clues about timestamps not preserved

comment:1 Changed 4 years ago by Tim Kosse

Resolution: rejected
Status: newclosed

Preserving timestamps on upload requires that the server supports the MFMT command. Your server does not support this command, hence timestamps cannot be preserved.

comment:2 Changed 4 years ago by Seagram

Hello Codesquid,

You are fast in replying, but how do you know the hosted server does not support MFMT command?

During the past years and months, it used to work, for the very same web site.

Maybe the hosting company did some changes on hosted servers, but how can I check that?

<edit>
Indeed, in the FileZilla Client log I activated, I can see that the server supports the MDTM extension. But there is no clue of MFMT extension. Is that enough information to assert the FTP server is the culprit?
</edit>

Thanks for your reply,
Seagram

comment:3 Changed 4 years ago by Tim Kosse

You are fast in replying, but how do you know the hosted server does not support MFMT command?

I connected to the server in question and sent the FEAT command.

Indeed, in the FileZilla Client log I activated, I can see that the server supports the MDTM extension. But there is no clue of MFMT extension. Is that enough information to assert the FTP server is the culprit?

RFC 3659 requires every server supporting MFMT to include it in the output of the FEAT command.

Note: See TracTickets for help on using tickets.