12 Facts About FTP

FTP is built on a client–server model architecture using separate control and data connections between the client and the server.

Support for the FTP protocol was first disabled in Google Chrome 88 in January 2021, followed by Firefox 88.

FTP needs two ports because it was originally designed to operate on top of Network Control Protocol, which was a simplex protocol that utilized two port addresses, establishing two connections, for two-way communications.

The standardization of TCP and UDP reduced the need for the use of two simplex ports for each application down to one duplex port, but the FTP protocol was never altered to only use one port, and continued using two for backwards compatibility.

FTP login uses normal username and password scheme for granting access.

Related searches

HTTP essentially fixes the bugs in FTP that made it inconvenient to use for many small ephemeral transfers as are typical in web pages.

FTP has a stateful control connection which maintains a current working directory and other flags, and each transfer requires a secondary connection through which the data are transferred.

When FTP is transferring over the data connection, the control connection is idle.

FireFTP is a browser extension designed as a full-featured FTP client, it could be run within Firefox in the past, but it's now recommend working with Waterfox.

FTP was not designed to be a secure protocol, and has many security weaknesses.

Trivial File Transfer Protocol is a simple, lock-step FTP that allows a client to get a file from or put a file onto a remote host.

TFTP lacks security and most of the advanced features offered by more robust file transfer protocols such as File Transfer Protocol.