We are still actively working on the spam issue.
Difference between revisions of "FTP"
(create page) |
(extend information, clean up page) |
||
| Line 3: | Line 3: | ||
== URI Scheme == | == URI Scheme == | ||
The FTP Protocol follows a simple URI scheme: | The FTP Protocol follows a simple URI scheme: | ||
| + | |||
<code>ftp://[email protected]:21/directory</code> | <code>ftp://[email protected]:21/directory</code> | ||
| + | |||
| + | Many software programs are able to connect to FTP servers, such as [[Web Browsers]]. In addition, file managers (usually) have native FTP availability. | ||
== Problems == | == Problems == | ||
In the official specification of the FTP Protocol, it uses a large amount of un-defined words that is hard to find the definitions to. Furthermore, even if it breaks it, the files transfered are converted to [[ASCII]]. Many people have switched over to [[SSH]] transfers. | In the official specification of the FTP Protocol, it uses a large amount of un-defined words that is hard to find the definitions to. Furthermore, even if it breaks it, the files transfered are converted to [[ASCII]]. Many people have switched over to [[SSH]] transfers. | ||
Revision as of 22:30, 31 October 2015
The File Transfer Protocol is a protocol developed in the early 1980's for fast transfer of files from server to server. It is slowly becoming defunct.
URI Scheme
The FTP Protocol follows a simple URI scheme:
ftp://[email protected]:21/directory
Many software programs are able to connect to FTP servers, such as Web Browsers. In addition, file managers (usually) have native FTP availability.
Problems
In the official specification of the FTP Protocol, it uses a large amount of un-defined words that is hard to find the definitions to. Furthermore, even if it breaks it, the files transfered are converted to ASCII. Many people have switched over to SSH transfers.
