FTP 212 Directory Status vs 228 Entering Long Passive Mode
Both FTP 212 (Directory Status) and 228 (Entering Long Passive Mode) belong to the 2xx Positive Completion category. 212 indicates that directory status reply. The server provides information about the current directory or a specified directory. Meanwhile, 228 means that entering Long Passive Mode. An extended version of passive mode that supports longer addresses, including IPv6. Largely superseded by EPSV (229).
Description
Directory status reply. The server provides information about the current directory or a specified directory.
When You See It
After issuing the STAT command on a directory, the server returns the directory listing or status information.
How to Fix
No fix needed — this is an informational response showing directory contents or status.
Description
Entering Long Passive Mode. An extended version of passive mode that supports longer addresses, including IPv6. Largely superseded by EPSV (229).
When You See It
After issuing the LPSV command on servers that support long addresses. Rarely seen in practice as EPSV is preferred.
How to Fix
No fix needed, but consider using EPSV (Extended Passive Mode) instead, which is more widely supported and simpler to parse.
Key Differences
FTP 212: Directory status reply. The server provides information about the current directory or a specified directory.
FTP 228: Entering Long Passive Mode. An extended version of passive mode that supports longer addresses, including IPv6. Largely superseded by EPSV (229).
You encounter 212 when after issuing the STAT command on a directory, the server returns the directory listing or status information.
You encounter 228 when after issuing the LPSV command on servers that support long addresses. Rarely seen in practice as EPSV is preferred.
When to Use Which
For 212 (Directory Status): No fix needed — this is an informational response showing directory contents or status. For 228 (Entering Long Passive Mode): No fix needed, but consider using EPSV (Extended Passive Mode) instead, which is more widely supported and simpler to parse.