[
https://issues.apache.org/jira/browse/NET-577?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14613264#comment-14613264
]
Sebb commented on NET-577:
--------------------------
It would of course be possible to allow for multiple leading spaces.
However this is definitely a violation of the RFC, so it seems wrong to do so.
What do other FTP clients do?
> Fails to parse FEAT response from Microsoft FTP Service
> -------------------------------------------------------
>
> Key: NET-577
> URL: https://issues.apache.org/jira/browse/NET-577
> Project: Commons Net
> Issue Type: Bug
> Components: FTP
> Affects Versions: 3.3
> Reporter: Jochen Kemnade
>
> This is probably rather a bug in the server implementation, but anyway.
> The response from a Microsoft FTP Service I'm trying to work with looks like
> that:
> {noformat}
> 211-FEAT
> SIZE
> MDTM
> 211 END
> {noformat}
> So, after parsing the response, the entries in the features map are {{
> SIZE}} and {{ MDTM}}.
> While it doesn't adhere to the RFC (there's supposed to be a single leading
> space for each feature), it should be possible to work around that kind of
> broken response.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
