FTP 220 Service Ready vs 350 File Action Pending
FTP 220 (Service Ready) is a 2xx Positive Completion response, while 350 (File Action Pending) is a 3xx Positive Intermediate response. 220 indicates that service ready for new user. This is the greeting message sent by the FTP server when a client first connects. In contrast, 350 means that requested file action pending further information. The server has accepted the first part of a two-step command and is waiting for the follow-up.
説明
Service ready for new user. This is the greeting message sent by the FTP server when a client first connects.
このコードが表示される場合
Immediately upon connecting to an FTP server. This is the welcome banner confirming the server is accepting connections.
解決方法
No fix needed — the server is ready. Proceed with USER and PASS commands to authenticate.
説明
Requested file action pending further information. The server has accepted the first part of a two-step command and is waiting for the follow-up.
このコードが表示される場合
After issuing RNFR (rename from) to specify which file to rename. The server is waiting for the RNTO (rename to) command.
解決方法
Send the follow-up command immediately — typically RNTO after RNFR, or REST followed by RETR for resumed transfers.
主な違い
220 is a 2xx Positive Completion response, while 350 is a 3xx Positive Intermediate response.
FTP 220: Service ready for new user. This is the greeting message sent by the FTP server when a client first connects.
FTP 350: Requested file action pending further information. The server has accepted the first part of a two-step command and is waiting for the follow-up.
You encounter 220 when immediately upon connecting to an FTP server. This is the welcome banner confirming the server is accepting connections.
You encounter 350 when after issuing RNFR (rename from) to specify which file to rename. The server is waiting for the RNTO (rename to) command.
どちらをいつ使うか
For 220 (Service Ready): No fix needed — the server is ready. Proceed with USER and PASS commands to authenticate. For 350 (File Action Pending): Send the follow-up command immediately — typically RNTO after RNFR, or REST followed by RETR for resumed transfers.