[
https://issues.apache.org/jira/browse/NET-590?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15222963#comment-15222963
]
Nadia Kanellopoulou commented on NET-590:
-----------------------------------------
After the reply command "250 Directory successfully changed.", I give the
command of an Invalid Connect, where probably a socket timeout occurs and the
addProtocolCommandListener does not produce any output for this action.
> In FTPClient, the Login function returns "true" for an invalid login
> --------------------------------------------------------------------
>
> Key: NET-590
> URL: https://issues.apache.org/jira/browse/NET-590
> Project: Commons Net
> Issue Type: Bug
> Components: FTP
> Reporter: Nadia Kanellopoulou
>
> We initiate: ftp = new FTPClient();
> If you follow Exactly this workflow:
> 1. Valid Connect (ftp.connect(validIP, 21))
> 2. Valid Login (boolean login = ftp.login("username", "correctPass"))
> 3. Valid Change directory (boolean changed =
> ftp.changeWorkingDirectory(correctRemoteDirectory))
> 4. Invalid Connect (ftp.connect(invalidIP, 21))
> 5. Valid Upload (boolean uploaded = ftp.storeFile(hostDir + fileName,
> inputStream))
> 6. Invalid Login (boolean login = ftp.login("username", "wrongPass"))
> The last action (Invalid Login) will return "true", although it should return
> "false"
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
