[
https://issues.apache.org/jira/browse/FTPSERVER-209?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Niklas Gustavsson closed FTPSERVER-209.
---------------------------------------
Resolution: Fixed
Fix Version/s: 1.0-M4
Assignee: Niklas Gustavsson
Agreed and fixed in rev 709413.
> onSite() method of DefaultFtplet called after command has been processed
> ------------------------------------------------------------------------
>
> Key: FTPSERVER-209
> URL: https://issues.apache.org/jira/browse/FTPSERVER-209
> Project: FtpServer
> Issue Type: Bug
> Components: Ftplets
> Affects Versions: 1.0-M3
> Environment: Windows XP, Sun JVM 1.5.0
> Reporter: Gary Bell
> Assignee: Niklas Gustavsson
> Priority: Minor
> Fix For: 1.0-M4
>
>
> According to the ftplet API documentation, the onSite() method is described
> thus:
> -- PASTE --
> This is SITE command start notification method. It gives a chance to
> implement custom SITE command. If this method returns SKIP or DISCONNECT, the
> existing SITE commands will not be executed.
> -- PASTE --
> But the onSite() method is only called inside the
> DefaultFtplet.afterCommand() method which means that the custom SITE command
> issued by the user always tries to be processed by the server, resulting in a
> "502 - Command SITE not implemented for xxx" message being displayed to the
> user even though the custom command is executed. Furthermore, returning
> FTPletResult.SKIP after processing the custom code to prevent further
> processing of the request by the server has no effect. For the onSite()
> method to work as per the documentation, it would have to be called in the
> beforeCommand() function.
> I can create sample code for clarification if you like.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
