[
https://issues.apache.org/jira/browse/NET-376?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13007957#comment-13007957
]
Sebb commented on NET-376:
--------------------------
Most (all?) FTP servers I have used always return the full format when LIST is
used, and names only when NLST is used.
It seems like a bug that the LIST format depends on whether the -a flag is
present or not - however the RFCs don't cover this as far as I can tell.
==
I have since found that ftp servers generally don't like it if the LIST command
contains a trailing space but no pathname.
This is probably the cause of the null socket - adding the command listener
should show that.
The FTP code allows for null pathname, treating it as a missing parameter.
It assumes that an empty pathname is valid, and prepends a space when
constructing the command.
Changing that might break user code, so at present I'm inclined to just
document the behaviour.
> setListHiddenFiles doesn't work for HFS file system running under zos
> ---------------------------------------------------------------------
>
> Key: NET-376
> URL: https://issues.apache.org/jira/browse/NET-376
> Project: Commons Net
> Issue Type: Bug
> Components: FTP
> Affects Versions: 2.2
> Environment: IBM z/OS running HFS
> Reporter: Colin Stone
>
> The implementation for setListHiddenFiles is essentially the use of a '-a'
> parameter appended to the LIST command. This retrieves the data in a
> different format to without the parameter and the parse engine used by
> initiateListParsing fails to read the lines returned.
> I suggest the parameter should have been '-al' for this scenario
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
