commons-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sebb (JIRA)" <>
Subject [jira] [Commented] (NET-566) UnixFTPEntryParser Drops Leading Spaces from File Names
Date Thu, 01 Jan 2015 16:53:13 GMT


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

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:
>             Project: Commons Net
>          Issue Type: Bug
>          Components: FTP
>    Affects Versions: 3.3
>         Environment: OSX client, Linux ftpd
>            Reporter: Gary Russell
> The {{UnixFTPEntryParser}} [regular expression |]
(line 106) consumes all spaces between the timestamp and the file name.
> The {{}} property ends up getting a value with stripped leading spaces.
> Reported by Spring Integration user at

This message was sent by Atlassian JIRA

View raw message