![]() ![]() As HTTPS uploading began to get more popular, people just stopped using FTP nearly as much. Even if many people didn't understand why FTP broke, what they did understand is that life did seem to work more successfully when they tried another technique, which is to just start moving onto using other protocols. Later, the believe that "passive mode" was magic "cure-all" got commonly replaced with a different belief, which is that FTP just commonly doesn't seem to work anymore (not nearly as well as it used to). They just learned that if FTP started acting weird, "passive mode" seemed to fix that weird problem that FTP experienced. (Many people didn't understand why FTP stopped working. FTP problems started to become more widespread.įor a while, people learned that "passive mode" seemed to be a magic "cure-all" technique that fixed the FTP problems. Many people consider that to be a bit hard to set up.Īs more organizations cared more about security, and cared less about FTP, people began to learn that FTP was becoming typically broken (meaning that more and more FTP servers were being challenging to use from more and more locations that people might try to use an FTP client at). In theory this could be fixed if the FTP server's firewall supports an FTP proxy which monitors traffic and opens up another port if needed. If the server has a firewall that only allows incoming traffic on specific port numbers, like port 21 for FTP, then even "passive mode" doesn't fix everything that is required to work. However, what "passive mode" actually fixed was just that one specific problem. Many people started to learn that "passive mode" fixed the FTP problems. That worked if the client had a firewall. So FTP clients could make outgoing connections, but incoming connections were blocked.Ī way around that was passive mode: The client sends a request using TCP port 21, then the server says it wants another connection using some random TCP port (e.g., 43728), and then the client makes a second connection using the specified random TCP port (e.g., 43728). This broke when clients started using firewalls to protect their stuff. Then the server received the request, and initiated a separate TCP connection to the client. The major universities and large organizations had rules of conduct, enforced by the respected institutions, and so people on the Internet (actually called the ARPAnet back then) were trusted.įTP was designed to have the client use a TCP connection to send a request for a file. ![]() I will also give you another alternative.įTP was written when the Internet was considered to be an experimental project. I know that probably wasn't the answer you were wanting to hear, but let me explain why it is actually necessary, and then you may be more inclined to do this. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |