Opened 14 years ago

Last modified 14 years ago

#920 closed Bug report

MDTM 550 Error

Reported by: inonsense Owned by:
Priority: normal Component: FileZilla Server
Keywords: Cc: inonsense, Tim Kosse, lesd
Component version: Operating system type:
Operating system version:

Description

It appears that MDTM is only partially implemented. ?
'MDTM<sp>filename' returns a correct timestamp, but
'MDTM<sp>timestamp<sp>filename' returns '500 File not
found' instead of changing the timestamp on the server.
That is the key to the MDTM function -- update the
timestamp on the server.
Since the FEAT command reports MDTM implementation, I
assume this is a bug.

Change History (3)

comment:1 Changed 14 years ago by Tim Kosse

MDTM cannot be used to set file timestamps.

Example: MDTM 20050726131800 foobar
What does this command do? Set timestamp for the file
'foobar' or get timestamp for the file '20050726131800 foobar'?
Due to this conflict, MDTM should only be used to get
timestamps.

comment:2 Changed 14 years ago by inonsense

As you can see from this discussion
<http://www.smartftp.com/phpBB2/viewtopic.php?t=6739>, many
FTP servers implement MDTM to permit changing the
modification time of on the server. Where the command is
ambiguous, i.e., two files exist where one is named
"YYYYMMDDHHMMSS foobar" and the other is named "foobar",
sending the command MTDM YYYYMMDDHHMMSS foobar returns the
modification time of "YYYYMMDDHHMMSS foobar" and does not
change the modification time of "foobar." Admittedly, this
is beyond the IETF draft, but it is not contrary to it and
many clients (for example, WS_FTP) expect to be able to
update modification time on the server by this method.

comment:3 Changed 14 years ago by lesd

Quote from codesquid:


MDTM cannot be used to set file timestamps.

Example: MDTM 20050726131800 foobar
What does this command do? Set timestamp for the file
'foobar' or get timestamp for the file '20050726131800 foobar'?
Due to this conflict, MDTM should only be used to get
timestamps.


This is a feature that I badly need and have been assured
that some other FTP Servers do implement it.

Surely the ambiguity is only there if a file of that name
*does* exist. If not then can FZ not accept the command as
a request to update the timestamp?

In addition, the likelyhood of having such a filename must
be so remote that the default should be to update file
'foobar' with what is a valid timestamp and only if the file
does not exist should FZ try to find a file with name
'20050726131800 foobar' and return its timesatamp.

Please could you re-consider, as this feature would make the
life of synchronization programs so much simpler.

Note: See TracTickets for help on using tickets.