350
FTP
350 File Action Pending
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.
Wenn Sie diesen Code 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.
Spezifikation
Vergleichen mit
Anleitungen
FTP Reply Codes: Understanding File Transfer Responses
DNS & Networking
TCP Three-Way Handshake and Connection Lifecycle
DNS & Networking
Essential Network Debugging Tools: ping, traceroute, mtr, and tcpdump
DNS & Networking
RFC 959: FTP Protocol Deep Dive
Protocol Deep Dives
TLS 1.3: Faster, Simpler, More Secure
Protocol Deep Dives
Migrating from FTP to SFTP: A Complete Transition Guide
Migration & Upgrades
HTTP Access Log Management: Rotation, Parsing, and Analysis
Production Infrastructure
Glossar
Status Code
TLS Handshake
TCP/IP
Three-Way Handshake
Port Number
Firewall
Proxy Server (Forward Proxy)
Socket
Request-Response Model
RFC (Request for Comments)
Connection-Oriented
Half-Duplex
Text vs Binary Protocol
FTP Active Mode
FTP Passive Mode
FTP Control Channel
FTP Data Channel
SFTP (SSH File Transfer Protocol)
FTPS (FTP Secure)
FTP Reply Code
FTP Anonymous Access
FTP Transfer Mode (ASCII vs Binary)
FTP Resume (REST Command)
SCP (Secure Copy Protocol)
FTP Chroot Jail
WebDAV (Web Distributed Authoring and Versioning)
rsync
FTP MLSD (Machine-Readable Listing)
FTP NAT Traversal
Transfer Integrity
FTP over TLS (RFC 4217)
File Locking
Bandwidth Throttling
TLS Versions