[
https://issues.apache.org/jira/browse/NET-339?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12914055#action_12914055
]
Sebb commented on NET-339:
--------------------------
OK, perhaps you can provide some more examples then?
Also, what does the SYST command return?
(Probably need to use "quote SYST" to send the command interactively)
Likewise the output of the STAT command would be useful, and the banner
details, for example as shown in the line prefixed with 220 below:
$ ftp -A ftp.mirrorservice.org
Connected to ftp.mirrorservice.org.
220 UK Mirror Service FTP server version 1.4 ready
ftp> quote SYST
215 UNIX Type: L8
ftp> quote STAT
211- maxwell-if-a.mirrorservice.org FTP server status:
211- Caching FTP server Version 1.4
211- Connected to n.n.n.n
211- Logged in anonymously
211- TYPE: ASCII, FORM: Nonprint; STRUcture: File; transfer MODE: Stream
211 No data connection
> 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.
