📄 416.htm
字号:
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=gb2312">
<title>CTerm非常精华下载</title>
</head>
<body bgcolor="#FFFFFF">
<table border="0" width="100%" cellspacing="0" cellpadding="0" height="577">
<tr><td width="32%" rowspan="3" height="123"><img src="DDl_back.jpg" width="300" height="129" alt="DDl_back.jpg"></td><td width="30%" background="DDl_back2.jpg" height="35"><p align="center"><a href="http://202.112.58.200"><font face="黑体"><big><big>Tsinghua</big></big></font></a></td></tr>
<tr>
<td width="68%" background="DDl_back2.jpg" height="44"><big><big><font face="黑体"><p align="center"> 嵌入式系统 (BM: turbolinux jacobw) </font></big></big></td></tr>
<tr>
<td width="68%" height="44" bgcolor="#000000"><font face="黑体"><big><big><p align="center"></big></big><a href="http://cterm.163.net"><img src="banner.gif" width="400" height="60" alt="banner.gif"border="0"></a></font></td>
</tr>
<tr><td width="100%" colspan="2" height="100" align="center" valign="top"><br><p align="center">[<a href="嵌入式系统.htm">回到开始</a>][<a href="398.htm">上一层</a>][<a href="417.htm">下一篇</a>]
<hr><p align="left"><small>发信人: hellow (收复台湾是我心), 信区: Embedded <br>
标 题: FTP <br>
发信站: BBS 水木清华站 (Sun Nov 5 09:28:41 2000) <br>
<br>
<br>
Network Working Group J. Postel <br>
Request for Comments: 959 J. Reynolds <br>
ISI <br>
Obsoletes RFC: 765 (IEN 149) October 1985 <br>
FILE TRANSFER PROTOCOL (FTP) <br>
Status of this Memo <br>
This memo is the official specification of the File Transfer <br>
Protocol (FTP). Distribution of this memo is unlimited. <br>
The following new optional commands are included in this edition of <br>
the specification: <br>
CDUP (Change to Parent Directory), SMNT (Structure Mount), STOU <br>
(Store Unique), RMD (Remove Directory), MKD (Make Directory), PWD <br>
(Print Directory), and SYST (System). <br>
Note that this specification is compatible with the previous edition. <br>
1. INTRODUCTION <br>
The objectives of FTP are 1) to promote sharing of files (computer <br>
programs and/or data), 2) to encourage indirect or implicit (via <br>
programs) use of remote computers, 3) to shield a user from <br>
variations in file storage systems among hosts, and 4) to transfer <br>
data reliably and efficiently. FTP, though usable directly by a user <br>
at a terminal, is designed mainly for use by programs. <br>
The attempt in this specification is to satisfy the diverse needs of <br>
users of maxi-hosts, mini-hosts, personal workstations, and TACs, <br>
with a simple, and easily implemented protocol design. <br>
This paper assumes knowledge of the Transmission Control Protocol <br>
(TCP) [2] and the Telnet Protocol [3]. These documents are contained <br>
in the ARPA-Internet protocol handbook [1]. <br>
2. OVERVIEW <br>
In this section, the history, the terminology, and the FTP model are <br>
discussed. The terms defined in this section are only those that <br>
have special significance in FTP. Some of the terminology is very <br>
specific to the FTP model; some readers may wish to turn to the <br>
section on the FTP model while reviewing the terminology. <br>
Postel & Reynolds [Page 1] <br>
<br>
<br>
RFC 959 October 1985 <br>
File Transfer Protocol <br>
2.1. HISTORY <br>
FTP has had a long evolution over the years. Appendix III is a <br>
chronological compilation of Request for Comments documents <br>
relating to FTP. These include the first proposed file transfer <br>
mechanisms in 1971 that were developed for implementation on hosts <br>
at M.I.T. (RFC 114), plus comments and discussion in RFC 141. <br>
RFC 172 provided a user-level oriented protocol for file transfer <br>
between host computers (including terminal IMPs). A revision of <br>
this as RFC 265, restated FTP for additional review, while RFC 281 <br>
suggested further changes. The use of a "Set Data Type" <br>
transaction was proposed in RFC 294 in January 1982. <br>
RFC 354 obsoleted RFCs 264 and 265. The File Transfer Protocol <br>
was now defined as a protocol for file transfer between HOSTs on <br>
the ARPANET, with the primary function of FTP defined as <br>
transfering files efficiently and reliably among hosts and <br>
allowing the convenient use of remote file storage capabilities. <br>
RFC 385 further commented on errors, emphasis points, and <br>
additions to the protocol, while RFC 414 provided a status report <br>
on the working server and user FTPs. RFC 430, issued in 1973, <br>
(among other RFCs too numerous to mention) presented further <br>
comments on FTP. Finally, an "official" FTP document was <br>
published as RFC 454. <br>
By July 1973, considerable changes from the last versions of FTP <br>
were made, but the general structure remained the same. RFC 542 <br>
was published as a new "official" specification to reflect these <br>
changes. However, many implementations based on the older <br>
specification were not updated. <br>
In 1974, RFCs 607 and 614 continued comments on FTP. RFC 624 <br>
proposed further design changes and minor modifications. In 1975, <br>
RFC 686 entitled, "Leaving Well Enough Alone", discussed the <br>
differences between all of the early and later versions of FTP. <br>
RFC 691 presented a minor revision of RFC 686, regarding the <br>
subject of print files. <br>
Motivated by the transition from the NCP to the TCP as the <br>
underlying protocol, a phoenix was born out of all of the above <br>
efforts in RFC 765 as the specification of FTP for use on TCP. <br>
This current edition of the FTP specification is intended to <br>
correct some minor documentation errors, to improve the <br>
explanation of some protocol features, and to add some new <br>
optional commands. <br>
Postel & Reynolds [Page 2] <br>
<br>
<br>
RFC 959 October 1985 <br>
File Transfer Protocol <br>
In particular, the following new optional commands are included in <br>
this edition of the specification: <br>
CDUP - Change to Parent Directory <br>
SMNT - Structure Mount <br>
STOU - Store Unique <br>
RMD - Remove Directory <br>
MKD - Make Directory <br>
PWD - Print Directory <br>
SYST - System <br>
This specification is compatible with the previous edition. A <br>
program implemented in conformance to the previous specification <br>
should automatically be in conformance to this specification. <br>
2.2. TERMINOLOGY <br>
ASCII <br>
The ASCII character set is as defined in the ARPA-Internet <br>
Protocol Handbook. In FTP, ASCII characters are defined to be <br>
the lower half of an eight-bit code set (i.e., the most <br>
significant bit is zero). <br>
access controls <br>
Access controls define users' access privileges to the use of a <br>
system, and to the files in that system. Access controls are <br>
necessary to prevent unauthorized or accidental use of files. <br>
It is the prerogative of a server-FTP process to invoke access <br>
controls. <br>
byte size <br>
There are two byte sizes of interest in FTP: the logical byte <br>
size of the file, and the transfer byte size used for the <br>
transmission of the data. The transfer byte size is always 8 <br>
bits. The transfer byte size is not necessarily the byte size <br>
in which data is to be stored in a system, nor the logical byte <br>
size for interpretation of the structure of the data. <br>
Postel & Reynolds [Page 3] <br>
⌨️ 快捷键说明
复制代码
Ctrl + C
搜索代码
Ctrl + F
全屏模式
F11
切换主题
Ctrl + Shift + D
显示快捷键
?
增大字号
Ctrl + =
减小字号
Ctrl + -