Talk:File Transfer Protocol

Anonymous FTP ?

I don't understand, in the article, why trivial FTP or Gopher are "alternatives" to anonymous FTP. How do those address the issues against anonymous FTP? And isn't TFTP only useful in a local network since it doesn't use the reliable TCP? —Długosz

TFTP and Gopher each use a single TCP connection instead of two in the way that FTP does. In situations where anonymous FTP would be used, but might be obstructed due to firewall issues because of the dual connection requirement, TFTP or Gopher can supply the same service -- anonymously retrieving a file without authentication -- to get around the firewall issue.

TFTP can theoretically work wherever UDP works, but you are correct, it is usually only useful on high speed LANs, though this is more due to latency issues -- TFTP only transmits one packet at a time, then waits for acknowledgement, much like the old XMODEM protocol for modems -- rather then because of reliability problems.dc

unique/static IP required for anonymous ftp??

Many webhosts claim that a unique IP is required to set up an anonymous ftp server. It is never explained why a static IP is necessary. Can the article address this point? Why can't we have anonymous download from an ftp server with a shared IP? Thanks. AugustinMa (talk) 09:27, 12 June 2008 (UTC)

As far as I know, as long as both client and server recognize each other IP for the whole length of an ftp session, the server can serve the client. Just follow the actions during an ftp session to see where each party must know the exact IP of the other. Other then that, the server can live in any IP. It also could change its IP from time to time. webhosts tend to use shortcuts for different reasons. 217.132.74.2 (talk) 17:16, 27 March 2015 (UTC)

Active mode without PORT command ?

According to RFC 959, PORT command is not needed because "There are defaults for both the user and server data ports, and under normal circumstances this command and its reply are not needed." but this fact is never mentioned in the article 125.161.204.150 (talk) 08:35, 26 July 2008 (UTC)

Those defaults are partially mentioned. Quoting the Communication and data transfer subsection

In active modes, the client starts listening for incoming data connections on port N+1 from the server

Here is the default for the client port. The default for the server port, 20, indeed not mentioned. But not saying anything about it, some might think that it is a fixed port. By the way, the following from text comment to the sentence I just quoted, namely

(the client sends the FTP command PORT N+1 to inform the server on which port it is listening)

is a bit odd. Why should the client announce something the server can calculate by itself? The answer is, probably:

1. N+1 is the default.
2. The client might tell another port.

Is that apparent from the text?

To conclude, I think the subsection should be rephrased.

217.132.74.2 (talk) 17:55, 27 March 2015 (UTC)

Need some specific info on proper server responses for various FTP client commands.

For each possible client command, I would like to know the proper server response. I'm creating my own FTP server software and want to know EXACTLY the signal that the server should send when the client calls PASV. I know it should contain the IP address and the port of the file server, but what is the format of that response? Is it "227 123.123.123.123:12345" or is it something else? Please post this kind of info here on Wikipedia. I can't find this specific info anywhere on the net. Animedude5555 (talk) 22:56, 22 September 2013 (UTC)

some correction is needed>>>>>>>>>>>>> — Preceding unsigned comment added by 120.89.119.32 (talk) 06:51, 1 June 2014 (UTC)

External links modified

Hello fellow Wikipedians,

I have just modified one external link on File Transfer Protocol. Please take a moment to review my edit. If you have any questions, or need the bot to ignore the links, or the page altogether, please visit this simple FaQ for additional information. I made the following changes:

• Replaced archive link http://webcache.googleusercontent.com/search?q=cache:http://slacksite.com/other/ftp.html with https://web.archive.org/web/20110504071617/http://slacksite.com:80/other/ftp.html on http://slacksite.com/other/ftp.html

When you have finished reviewing my changes, you may follow the instructions on the template below to fix any issues with the URLs.

This message was posted before February 2018. After February 2018, "External links modified" talk page sections are no longer generated or monitored by InternetArchiveBot. No special action is required regarding these talk page notices, other than regular verification using the archive tool instructions below. Editors have permission to delete these "External links modified" talk page sections if they want to de-clutter talk pages, but see the RfC before doing mass systematic removals. This message is updated dynamically through the template {{source check}} (last update: 5 June 2024).

• If you have discovered URLs which were erroneously considered dead by the bot, you can report them with this tool.
• If you found an error with any archives or the URLs themselves, you can fix them with this tool.

Cheers.—InternetArchiveBot (Report bug) 13:22, 31 December 2016 (UTC)