Package org.apache.ftpserver.ftplet

Interface FtpReply

All Known Subinterfaces:
DataTransferFtpReply, FileActionFtpReply, RenameFtpReply
All Known Implementing Classes:
DefaultFtpReply
public interface FtpReply
Interface for a reply to an FTP request.
Author:
Apache MINA Project

  • Field Details

    • REPLY_110_RESTART_MARKER_REPLY

      static final int REPLY_110_RESTART_MARKER_REPLY
      110 Restart marker reply. In this case, the text is exact and not left to the particular implementation; it must read: MARK yyyy = mmmm Where yyyy is User-process data stream marker, and mmmm server's equivalent marker (note the spaces between markers and "=").
      See Also:

    • REPLY_120_SERVICE_READY_IN_NNN_MINUTES

      static final int REPLY_120_SERVICE_READY_IN_NNN_MINUTES
      120 Service ready in nnn minutes.
      See Also:

    • REPLY_125_DATA_CONNECTION_ALREADY_OPEN

      static final int REPLY_125_DATA_CONNECTION_ALREADY_OPEN
      125 Data connection already open; transfer starting.
      See Also:

    • REPLY_150_FILE_STATUS_OKAY

      static final int REPLY_150_FILE_STATUS_OKAY
      150 File status okay; about to open data connection.
      See Also:

    • REPLY_200_COMMAND_OKAY

      static final int REPLY_200_COMMAND_OKAY
      200 Command okay.
      See Also:

    • REPLY_202_COMMAND_NOT_IMPLEMENTED

      static final int REPLY_202_COMMAND_NOT_IMPLEMENTED
      202 Command not implemented, superfluous at this site.
      See Also:

    • REPLY_211_SYSTEM_STATUS_REPLY

      static final int REPLY_211_SYSTEM_STATUS_REPLY
      211 System status, or system help reply.
      See Also:

    • REPLY_212_DIRECTORY_STATUS

      static final int REPLY_212_DIRECTORY_STATUS
      212 Directory status.
      See Also:

    • REPLY_213_FILE_STATUS

      static final int REPLY_213_FILE_STATUS
      213 File status.
      See Also:

    • REPLY_214_HELP_MESSAGE

      static final int REPLY_214_HELP_MESSAGE
      214 Help message. On how to use the server or the meaning of a particular non-standard command. This reply is useful only to the human user.
      See Also:

    • REPLY_215_NAME_SYSTEM_TYPE

      static final int REPLY_215_NAME_SYSTEM_TYPE
      215 NAME system type. Where NAME is an official system name from the list in the Assigned Numbers document.
      See Also:

    • REPLY_220_SERVICE_READY

      static final int REPLY_220_SERVICE_READY
      220 Service ready for new user.
      See Also:

    • REPLY_221_CLOSING_CONTROL_CONNECTION

      static final int REPLY_221_CLOSING_CONTROL_CONNECTION
      Service closing control connection. Logged out if appropriate.
      See Also:

    • REPLY_225_DATA_CONNECTION_OPEN_NO_TRANSFER_IN_PROGRESS

      static final int REPLY_225_DATA_CONNECTION_OPEN_NO_TRANSFER_IN_PROGRESS
      225 Data connection open; no transfer in progress.
      See Also:

    • REPLY_226_CLOSING_DATA_CONNECTION

      static final int REPLY_226_CLOSING_DATA_CONNECTION
      Closing data connection. Requested file action successful (for example, file transfer or file abort).
      See Also:

    • REPLY_227_ENTERING_PASSIVE_MODE

      static final int REPLY_227_ENTERING_PASSIVE_MODE
      227 Entering Passive Mode (h1,h2,h3,h4,p1,p2).
      See Also:

    • REPLY_230_USER_LOGGED_IN

      static final int REPLY_230_USER_LOGGED_IN
      230 User logged in, proceed.
      See Also:

    • REPLY_250_REQUESTED_FILE_ACTION_OKAY

      static final int REPLY_250_REQUESTED_FILE_ACTION_OKAY
      250 Requested file action okay, completed.
      See Also:

    • REPLY_257_PATHNAME_CREATED

      static final int REPLY_257_PATHNAME_CREATED
      257 "PATHNAME" created.
      See Also:

    • REPLY_331_USER_NAME_OKAY_NEED_PASSWORD

      static final int REPLY_331_USER_NAME_OKAY_NEED_PASSWORD
      331 User name okay, need password.
      See Also:

    • REPLY_332_NEED_ACCOUNT_FOR_LOGIN

      static final int REPLY_332_NEED_ACCOUNT_FOR_LOGIN
      332 Need account for login.
      See Also:

    • REPLY_350_REQUESTED_FILE_ACTION_PENDING_FURTHER_INFORMATION

      static final int REPLY_350_REQUESTED_FILE_ACTION_PENDING_FURTHER_INFORMATION
      350 Requested file action pending further information.
      See Also:

    • REPLY_421_SERVICE_NOT_AVAILABLE_CLOSING_CONTROL_CONNECTION

      static final int REPLY_421_SERVICE_NOT_AVAILABLE_CLOSING_CONTROL_CONNECTION
      421 Service not available, closing control connection. This may be a reply to any command if the service knows it must shut down.
      See Also:

    • REPLY_425_CANT_OPEN_DATA_CONNECTION

      static final int REPLY_425_CANT_OPEN_DATA_CONNECTION
      425 Can't open data connection.
      See Also:

    • REPLY_426_CONNECTION_CLOSED_TRANSFER_ABORTED

      static final int REPLY_426_CONNECTION_CLOSED_TRANSFER_ABORTED
      426 Connection closed; transfer aborted.
      See Also:

    • REPLY_450_REQUESTED_FILE_ACTION_NOT_TAKEN

      static final int REPLY_450_REQUESTED_FILE_ACTION_NOT_TAKEN
      450 Requested file action not taken. File unavailable (e.g., file busy).
      See Also:

    • REPLY_451_REQUESTED_ACTION_ABORTED

      static final int REPLY_451_REQUESTED_ACTION_ABORTED
      451 Requested action aborted: local error in processing.
      See Also:

    • REPLY_452_REQUESTED_ACTION_NOT_TAKEN

      static final int REPLY_452_REQUESTED_ACTION_NOT_TAKEN
      452 Requested action not taken. Insufficient storage space in system.
      See Also:

    • REPLY_500_SYNTAX_ERROR_COMMAND_UNRECOGNIZED

      static final int REPLY_500_SYNTAX_ERROR_COMMAND_UNRECOGNIZED
      500 Syntax error, command unrecognized. This may include errors such as command line too long.
      See Also:

    • REPLY_501_SYNTAX_ERROR_IN_PARAMETERS_OR_ARGUMENTS

      static final int REPLY_501_SYNTAX_ERROR_IN_PARAMETERS_OR_ARGUMENTS
      501 Syntax error in parameters or arguments.
      See Also:

    • REPLY_502_COMMAND_NOT_IMPLEMENTED

      static final int REPLY_502_COMMAND_NOT_IMPLEMENTED
      502 Command not implemented.
      See Also:

    • REPLY_503_BAD_SEQUENCE_OF_COMMANDS

      static final int REPLY_503_BAD_SEQUENCE_OF_COMMANDS
      503 Bad sequence of commands.
      See Also:

    • REPLY_504_COMMAND_NOT_IMPLEMENTED_FOR_THAT_PARAMETER

      static final int REPLY_504_COMMAND_NOT_IMPLEMENTED_FOR_THAT_PARAMETER
      504 Command not implemented for that parameter.
      See Also:

    • REPLY_530_NOT_LOGGED_IN

      static final int REPLY_530_NOT_LOGGED_IN
      530 Not logged in.
      See Also:

    • REPLY_532_NEED_ACCOUNT_FOR_STORING_FILES

      static final int REPLY_532_NEED_ACCOUNT_FOR_STORING_FILES
      532 Need account for storing files.
      See Also:

    • REPLY_550_REQUESTED_ACTION_NOT_TAKEN

      static final int REPLY_550_REQUESTED_ACTION_NOT_TAKEN
      550 Requested action not taken. File unavailable (e.g., file not found, no access).
      See Also:

    • REPLY_551_REQUESTED_ACTION_ABORTED_PAGE_TYPE_UNKNOWN

      static final int REPLY_551_REQUESTED_ACTION_ABORTED_PAGE_TYPE_UNKNOWN
      551 Requested action aborted: page type unknown.
      See Also:

    • REPLY_552_REQUESTED_FILE_ACTION_ABORTED_EXCEEDED_STORAGE

      static final int REPLY_552_REQUESTED_FILE_ACTION_ABORTED_EXCEEDED_STORAGE
      552 Requested file action aborted. Exceeded storage allocation (for current directory or dataset).
      See Also:

    • REPLY_553_REQUESTED_ACTION_NOT_TAKEN_FILE_NAME_NOT_ALLOWED

      static final int REPLY_553_REQUESTED_ACTION_NOT_TAKEN_FILE_NAME_NOT_ALLOWED
      553 Requested action not taken. File name not allowed.
      See Also:

  • Method Details

    • getCode

      int getCode()
      The reply code.
      Returns:
      The reply code

    • getMessage

      String getMessage()
      The reply message, might be multiple lines.
      Returns:
      The reply message

    • getSentTime

      long getSentTime()
      Returns the timestamp (in milliseconds since the epoch time) when this reply was sent.
      Returns:
      the timestamp (in milliseconds since the epoch time) when this reply was sent.

    • toString

      String toString()
      Must implement toString to format the reply as described in the RFC. Most important is the handling of multi-line replies.
      Overrides:
      toString in class Object
      Returns:
      The formated reply

    • isPositive

      boolean isPositive()
      Tells whether or not this reply indicates a positive completion.
      Returns:
      true, if this reply is a positive completion or positive intermediate reply; false, otherwise.