FTP 125 Data Connection Open vs 350 File Action Pending
FTP 125 (Data Connection Open) is a 1xx Positive Preliminary response, while 350 (File Action Pending) is a 3xx Positive Intermediate response. 125 indicates that the data connection is already open and the transfer is beginning. No need to open a new data connection. 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.
Description
The data connection is already open and the transfer is beginning. No need to open a new data connection.
When You See It
When the server reuses an existing data connection for a file transfer instead of opening a new one.
How to Fix
No fix needed — the transfer is starting immediately. Your client should begin reading or writing data on the existing connection.
Description
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.
When You See It
After issuing RNFR (rename from) to specify which file to rename. The server is waiting for the RNTO (rename to) command.
How to Fix
Send the follow-up command immediately — typically RNTO after RNFR, or REST followed by RETR for resumed transfers.
Key Differences
125 is a 1xx Positive Preliminary response, while 350 is a 3xx Positive Intermediate response.
FTP 125: The data connection is already open and the transfer is beginning. No need to open a new data connection.
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 125 when when the server reuses an existing data connection for a file transfer instead of opening a new one.
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.
When to Use Which
For 125 (Data Connection Open): No fix needed — the transfer is starting immediately. Your client should begin reading or writing data on the existing connection. For 350 (File Action Pending): Send the follow-up command immediately — typically RNTO after RNFR, or REST followed by RETR for resumed transfers.