Submit a ticketCall us

WebinarUpcoming Webinar: Know What’s Changed – with NEW Server Configuration Monitor

Change management in IT is critical. But, even with a good change management process, changes are too often not correctly tracked, if at all. The configuration of your servers and applications is a key factor in their performance, availability, and security. Many incidents can be tracked back to an authorized (and sometimes unauthorized) configuration change, whether to a system file, configuration file, or Windows® Registry entry. Join SolarWinds VP of product management Brandon Shopp to discover how the new SolarWinds® Server Configuration Monitor is designed to help you.

Register now.

Home > Success Center > Serv-U Managed File Transfer & Serv-U FTP Server > Serv-U - Knowledgebase Articles > 502 FTP response code

502 FTP response code

Updated May 8, 2017

Overview

This article explains why the 502 FTP response code is sent.

Environment

All Serv-U versions

Detail

A 502 code may be sent in response to any FTP command that the server does not support. It is a permanent negative reply, which means the client is discouraged from sending the command again since the server will respond with the same reply code. The original FTP specification dictates a minimum implementation for all FTP servers with a list of required commands. Because of this, a 502 reply code should not be sent in response to a required command.

Example response

502 Command not implemented

Possible command

A 502 response code may be sent to any FTP command that the server does not support.

 

 

Last modified

Tags

Classifications

Public