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 "Tony (JIRA)" <ji...@apache.org> on 2007/05/23 20:09:16 UTC
[jira] Created: (FTPSERVER-89) Full support for MDTM
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
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.
[jira] Closed: (FTPSERVER-89) Full support for MDTM
Posted by "Niklas Gustavsson (JIRA)" <ji...@apache.org>.
[ 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.
[jira] Commented: (FTPSERVER-89) Full support for MDTM
Posted by "Niklas Gustavsson (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/FTPSERVER-89?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12498622 ]
Niklas Gustavsson commented on FTPSERVER-89:
--------------------------------------------
I looked some further into this. Is there actually an RFC for setting the modified time? The text above seems to come from the documentation of TitanFTP rather than an RFC. In fact, the RFC draft (http://tools.ietf.org/html/draft-ietf-ftpext-mlst-12#section-3) does not seem to cover changes to the modified time, or am I missing something?
Also, when using the syntax described above, how would one distinguish between and timestamp+filename and a filename containing a timestamp and a space (the RFC draft contains such an example)?
> 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
> 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.
[jira] Commented: (FTPSERVER-89) Full support for MDTM
Posted by "Niklas Gustavsson (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/FTPSERVER-89?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12498388 ]
Niklas Gustavsson commented on FTPSERVER-89:
--------------------------------------------
No, this is not supported, and we would even fail on a command containing the timestamp.
Feel free to provide a patch if you want to speed up the time to get this into the code.
> 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
> 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.
[jira] Commented: (FTPSERVER-89) Full support for MDTM
Posted by "Tony Zhou (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/FTPSERVER-89?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12499279 ]
Tony Zhou commented on FTPSERVER-89:
------------------------------------
Yes, you are right. After check I found the material I got from Google is not a RFC record. This way of using MDTM may have ambiguous meanings for a file name with timestamps in it. It seems that there are no formal solutions to change the remote file's timestamp?
> 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
> 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.