[
https://issues.apache.org/jira/browse/FTPSERVER-364?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Emmanuel Lécharny updated FTPSERVER-364:
----------------------------------------
Fix Version/s: 1.1.5
(was: 1.1.2)
> Incorrect behavior when max logins limit is reached
> ---------------------------------------------------
>
> Key: FTPSERVER-364
> URL: https://issues.apache.org/jira/browse/FTPSERVER-364
> Project: FtpServer
> Issue Type: Bug
> Components: Core
> Affects Versions: 1.0.4
> Reporter: Sai Pullabhotla
> Priority: Minor
> Fix For: 1.0.0-M1, 1.1.5
>
>
> When max logins limit is reached, the server currently behaves as below:
> Accepts connections from new clients and keeps them open
> Let's the new clients issue some commands (like I can go ahead and issue as
> many invalid commands as I want)
> When the client sends a valid USER command with username argument, the server
> then figures out that it has reached the max limit.
> I think t would probably makes sense to change the behavior as follows:
> When a new client comes in, check if we reached the cap, and if so, send 421
> message right away, instead of sending a 2xxx reply.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
