110, 120, 125, 150 FTP Response Codes

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

Where yyyy is the client data stream marker, and mmmm is the server’s equivalent marker. The spaces between the markers and = are required.

Example response

110 Restart marker reply.

Possible commands:

• APPE
• RETR
• STOR
• STOU

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.

Possible command:

• REIN

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.

Example response

125 Data connection already opened; transfer starting.

Possible commands:

• LIST
• MLSD
• RETR
• STOR
• NLST
• STOU

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.

Example response

150 File status okay; about to open data connection.

Possible commands:

• LIST
• MLSD
• NLST
• RETR
• STOR
• STOU
• THMB

• 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