[prev in list] [next in list] [prev in thread] [next in thread] 

List:       mina-dev
Subject:    [jira] [Commented] (FTPSERVER-413) STAT command returns wrong 200
From:       "Sebb (JIRA)" <jira () apache ! org>
Date:       2011-05-31 0:34:47
Message-ID: 520605351.54673.1306802087343.JavaMail.tomcat () hel ! zones ! apache ! org
[Download RAW message or body]


    [ https://issues.apache.org/jira/browse/FTPSERVER-413?page=com.atlassian.jira.plug \
in.system.issuetabpanels:comment-tabpanel&focusedCommentId=13041347#comment-13041347 \
] 

Sebb commented on FTPSERVER-413:
--------------------------------

Or in the case of STAT without a parameter:

ftp> quote STAT
211-Apache FtpServer
Connected to 127.0.0.1
Connected from 127.0.0.1
Logged in as anonymous
211 End of status.

which agrees with the RFC

> STAT command returns wrong 200 state
> ------------------------------------
> 
> Key: FTPSERVER-413
> URL: https://issues.apache.org/jira/browse/FTPSERVER-413
> Project: FtpServer
> Issue Type: Bug
> Affects Versions: 1.0.5
> Reporter: Mark Struberg
> Assignee: Niklas Gustavsson
> Fix For: 1.0.6, 1.1.0
> 
> 
> I'm now using MINA FtpServer for the Integration Tests of Apache mavens wagon-ftp. \
> While upgrding from a 8 year old avalon based ftpserver jar, I figured that a unit \
> test is broken.  This has to do with FtpServer returning a 200 state which is imo \
> invalid. According to the officla RFC http://www.faqs.org/rfcs/rfc959.html STAT may \
> only return the following codes: STAT
> 211, 212, 213
> 450
> 500, 501, 502, 421, 530
> I think returning 200 (command ok) after a STAT command is a bug.
> 

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira


[prev in list] [next in list] [prev in thread] [next in thread]