Submit a ticketCall us

Don’t fall victim to a ransomware attack
Backups are helpful, but sometimes that’s not enough to protect your business against ransomware. At our live webcast we will discuss how to protect against ransomware attacks with SolarWinds® Patch Manager and how to leverage log data to detect ransomware. Register now for our live webcast.

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
20:10, 8 May 2017

Tags

Classifications

Public