[
https://issues.apache.org/jira/browse/NET-339?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12914059#action_12914059
]
Bram commented on NET-339:
--------------------------
the ftp servers does not seem to support the stat command...
ftp> open n.n.n.n
Connected to n.n.n.n.
220 Service ready for new user.
Name (n.n.n.n:root): admin
331 User name okay, need password.
Password:
230 User logged in, proceed.
Remote system type is Windows_CE.
ftp> quote syst
215 Windows_CE version 6.0.
ftp> dir
229 Entering extended passive mode (|||53321|).
125 Data connection already open; transfer starting.
01-01-98 05:00 <DIR> Network
01-01-98 05:00 <DIR> StorageCard
09-13-10 20:08 <DIR> Recycled
09-06-06 19:00 69 desktop.ini
09-13-10 13:08 23 Control Panel.lnk
09-13-10 13:08 <DIR> My Documents
09-13-10 13:08 <DIR> Program Files
09-13-10 13:08 <DIR> Temp
09-13-10 13:08 <DIR> Windows
226 Closing data connection.
ftp> quote stat
500 Syntax error, command unrecognized.
ftp> quote help
214-The following commands are implemented.
USER PASS QUIT PORT PASV
TYPE RETR STOR RNFR RNTO
DELE CWD XCWD LIST NLST
SYST HELP NOOP MKD XMKD
RMD XRMD PWD XPWD CDUP
XCUP MODE STRU
214 HELP command successful.
> Incorrect parsing of timestamp on windows
> -----------------------------------------
>
> Key: NET-339
> URL: https://issues.apache.org/jira/browse/NET-339
> Project: Commons Net
> Issue Type: Bug
> Components: FTP
> Affects Versions: 2.0
> Environment: Windows
> Reporter: Bram
> Priority: Minor
> Attachments: NET-339_v2.patch
>
>
> Somewhere in the past the timestamp format returned by windows/the windows
> ftp server changed.
> In the past the timestamp had a format like: '09-21-10 06:00PM'.
> The 'current' format however is: '09-21-10 18:00'.
> In version 1.4 this resulted in no files being displayed because parsing the
> timestamp fails;
> In version 2 this results in the files being displayed but without the
> timestamp.
> (This is the result of change 645299)
> The attached patch updates the code so that it detects both the old and the
> new format of the timestamp.
> A bug that also mentions this, or at least the comments,
> https://issues.apache.org/jira/browse/NET-50
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
