Submit a ticketCall us

Systems Monitoring for Dummies
Our new eBook will teach you the fundamentals and help you create monitors and alerts that are effective, meaningful, and actionable. Monitoring is more than a checkbox on your to-do list. This free eBook will give you practical advice to help you succeed in all aspects of monitoring – discovery, alerting, remediation, and troubleshooting. Don’t miss out on this indispensable resource for newbies, experienced IT pros, and everyone in between. Register Now.

Home > Success Center > Serv-U Managed File Transfer & Serv-U FTP Server > 350 FTP response code

350 FTP response code

Updated May 3, 2017

Overview

This article provides information on 350 FTP response code.

 

Environment

All Serv-U versions

Detail

A 350 response code is sent by the server in response to a file-related command that requires further commands in order for the operation to be completed. The original FTP specification identifies two instances where this reply code can be used. The first is in response to a REST command, which would indicate that the server has received the restart marker and is pending the initiation of file transfer to resume the transfer at the marker point. The second is in positive response to the RNFR command where the server is waiting for an RNTO command to complete the file rename operation.

Example response

350 Requested file action pending further information.

Possible command

 

 

 

Last modified

Tags

Classifications

Public