FTP 202 Command Superfluous vs 350 File Action Pending
FTP 202 (Command Superfluous) is a 2xx Positive Completion response, while 350 (File Action Pending) is a 3xx Positive Intermediate response. 202 indicates that the command is not implemented but is recognized as superfluous. The server acknowledges the command but it has no effect. 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.
Beschreibung
The command is not implemented but is recognized as superfluous. The server acknowledges the command but it has no effect.
Wann Sie es sehen
When you send a command the server recognizes but considers unnecessary, such as ALLO on a server that does not require pre-allocation.
Wie man es behebt
No fix needed — the server is telling you the command is not necessary. You can safely ignore this response and continue.
Beschreibung
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.
Wann Sie es sehen
After issuing RNFR (rename from) to specify which file to rename. The server is waiting for the RNTO (rename to) command.
Wie man es behebt
Send the follow-up command immediately — typically RNTO after RNFR, or REST followed by RETR for resumed transfers.
Wesentliche Unterschiede
202 is a 2xx Positive Completion response, while 350 is a 3xx Positive Intermediate response.
FTP 202: The command is not implemented but is recognized as superfluous. The server acknowledges the command but it has no effect.
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 202 when when you send a command the server recognizes but considers unnecessary, such as ALLO on a server that does not require pre-allocation.
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.
Wann welchen verwenden
For 202 (Command Superfluous): No fix needed — the server is telling you the command is not necessary. You can safely ignore this response and continue. For 350 (File Action Pending): Send the follow-up command immediately — typically RNTO after RNFR, or REST followed by RETR for resumed transfers.