You are viewing a plain text version of this content. The canonical link for it is here.
Posted to ftpserver-dev@incubator.apache.org by "Niklas Gustavsson (JIRA)" <ji...@apache.org> on 2007/08/14 21:11:37 UTC
[jira] Closed: (FTPSERVER-89) Full support for MDTM
[ https://issues.apache.org/jira/browse/FTPSERVER-89?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Niklas Gustavsson closed FTPSERVER-89.
--------------------------------------
Resolution: Won't Fix
Assignee: Niklas Gustavsson
Seems like we can't fix this as it's not in any official RFC
> Full support for MDTM
> ---------------------
>
> Key: FTPSERVER-89
> URL: https://issues.apache.org/jira/browse/FTPSERVER-89
> Project: FtpServer
> Issue Type: Improvement
> Components: Core
> Affects Versions: WISHLIST
> Reporter: Tony Zhou
> Assignee: Niklas Gustavsson
> Priority: Minor
>
> The MDTM support seems incomplete in current system, right? The current MDTM supports only retrieving of file's last modification time, rather than changing the file's last modification time.
> Here is the full MDTM spec:
> Overview
> The MDTM command provides the ability to retrieve and set date/time information for a file on the server. If a single argument is specified, it must be a filename for which date/time information is being requested. If two arguments are supplied, the first argument is the date/time to apply to the file, and the remaining argument is the file to apply that time to. When specifying the date/time information, it must be in the following format:
> YYYYMMDD[HHXXSS]
> Y - four digit year
> M - two digit month
> D - two digit day of the month
> H - two digit hour (0..23)
> X - two digit minute (0..59)
> S - two digit second (0..59)
>
> Format
> MDTM <name><crlf> (returns the date/time for the file)
> MDTM YYYYMMDD <name><crlf> (sets date for the file)
> MDTM YYYYMMDDHHXXSS <name><crlf> (sets date/time for the file)
> Returns
> 213 - Command successful.
> 421 - The server is off-line or is going off-line.
> 501 - Syntax error in parameters or arguments. This usually results from an invalid or missing file name.
> 502 - Command not implemented. This will be returned if MDTM support is not enabled on the server.
> 530 - No user is currently authenticated on the command channel.
> 553 - File name not allowed, or file type banned.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.