Mailing-List: contact issues-help@commons.apache.org; run by ezmlm
Precedence: bulk
Reply-To: issues@commons.apache.org
Date: Thu, 9 Jul 2015 10:29:04 +0000 (UTC)
From: "Jochen Kemnade (JIRA)" <jira@apache.org>
To: issues@commons.apache.org
Message-ID: <JIRA.12841679.1435666562000.141240.1436437744640@Atlassian.JIRA>
In-Reply-To: <JIRA.12841679.1435666562000@Atlassian.JIRA>
References: <JIRA.12841679.1435666562000@Atlassian.JIRA>
 <JIRA.12841679.1435666562063@arcas>
Subject: [jira] [Commented] (NET-577) Fails to parse FEAT response from
 Gene6 FTP server
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/NET-577?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14620284#comment-14620284 ] 

Jochen Kemnade commented on NET-577:
------------------------------------

It's a Gene6 FTP server 3.9.0 (Build 2) (www.g6ftpserver.com). I haven't checked whether the current version also behaves like that. And yes, the behavior is wrong according to the RFC.

> Fails to parse FEAT response from Gene6 FTP server
> --------------------------------------------------
>
>                 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)