[
https://issues.apache.org/jira/browse/NET-566?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14262596#comment-14262596
]
Sebb commented on NET-566:
--------------------------
Thanks for the very clear bug report.
Are Unix ftp listings guaranteed to always have just one space after the
timestamp?
As far as I can tell, there is no standard format; the listing is intended to
be human readable, not machine parseable.
What if some servers return 2 spaces?
So before the Regex can be changed, we need to be sure that changing it would
not break other usages.
Note that if the server supports MLSD or MLST that would be a better solution.
> UnixFTPEntryParser Drops Leading Spaces from File Names
> -------------------------------------------------------
>
> Key: NET-566
> URL: https://issues.apache.org/jira/browse/NET-566
> Project: Commons Net
> Issue Type: Bug
> Components: FTP
> Affects Versions: 3.3
> Environment: OSX client, Linux ftpd
> Reporter: Gary Russell
>
> The {{UnixFTPEntryParser}} [regular expression |
> http://svn.apache.org/viewvc/commons/proper/net/trunk/src/main/java/org/apache/commons/net/ftp/parser/UnixFTPEntryParser.java?view=markup]
> (line 106) consumes all spaces between the timestamp and the file name.
> The {{FTPFile.name}} property ends up getting a value with stripped leading
> spaces.
> Reported by Spring Integration user at https://jira.spring.io/browse/INT-3591
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
