This article explains 100 series response code.
The requested action is being initiated, expect another reply before proceeding with a new command.
110 FTP Response code
Unlike most FTP responses, the text of this response is specified and not left up to the specific server implementation. It must read:
MARK yyyy = mmmm
yyyy is the client data stream marker, and
mmmm is the server's equivalent marker. The spaces between the markers and = are required.
110 Restart marker reply.
120 FTP Response code
A 120 code is a positive preliminary response to the client. This indicates that the server accepted and has begun the processing of the command. The client should wait until another response is received before proceeding.
125 FTP Response code
The server may use this code in response to a command initiating a file transfer if the data connection is already established. After sending or receiving this response, the server or client may begin sending data over the data connection.
125 Data connection already opened; transfer starting.
150 FTP Response code
The server may use this reply code in response to a command initiating a file transfer before establishing the data connection over which the file transfer will occur. A PASV or PORT command should have been issued prior to the command
receiving the 150 response code. After sending or receiving this response, the server/client may begin sending data over the data connection.
150 File status okay; about to open data connection.
- 202, 211, 212, 213 FTP response codes
- 214, 215, 220, 221 FTP response codes
- 225, 225, 227, 230 FTP response codes
- 232, 234, 250, 253, 257 FTP response codes
- 331, 332, 334, 336, 350 FTP response codes
- 401, 421, 425, 426 FTP response codes
- 431, 450, 451, 452 FTP response codes
- 500, 501, 502, 503, 504 FTP response codes
- 530, 532, 533, 534, 535, FTP response codes
- 536, 550, 551, 552, 553 FTP response codes