📄 rfc2616.4up.ps
字号:
( The Hypertext Transfer Protocol \(HTTP\) is an application-level) s5 439 M( protocol for distributed, collaborative, hypermedia information) s5 426 M( systems. HTTP has been in use by the World-Wide Web global) s5 413 M( information initiative since 1990. The first version of HTTP,) s5 400 M( referred to as HTTP/0.9, was a simple protocol for raw data transfer) s5 387 M( across the Internet. HTTP/1.0, as defined by RFC 1945 [6], improved) s5 374 M( the protocol by allowing messages to be in the format of MIME-like) s5 361 M( messages, containing metainformation about the data transferred and) s5 348 M( modifiers on the request/response semantics. However, HTTP/1.0 does) s5 335 M( not sufficiently take into consideration the effects of hierarchical) s5 322 M( proxies, caching, the need for persistent connections, or virtual) s5 309 M( hosts. In addition, the proliferation of incompletely-implemented) s5 296 M( applications calling themselves "HTTP/1.0" has necessitated a) s5 283 M( protocol version change in order for two communicating applications) s5 270 M( to determine each other's true capabilities.) s5 244 M( This specification defines the protocol referred to as "HTTP/1.1".) s5 231 M( This protocol includes more stringent requirements than HTTP/1.0 in) s5 218 M( order to ensure reliable implementation of its features.) s5 192 M( Practical information systems require more functionality than simple) s5 179 M( retrieval, including search, front-end update, and annotation. HTTP) s5 166 M( allows an open-ended set of methods and headers that indicate the) s5 153 M( purpose of a request [47]. It builds on the discipline of reference) s5 140 M( provided by the Uniform Resource Identifier \(URI\) [3], as a location) s5 127 M( \(URL\) [4] or name \(URN\) [20], for indicating the resource to which a) s5 49 M(Fielding, et al. Standards Track [Page 7]) s_R%Page: (8) 8%BeginPageSetup_S% N-up sub-page 4/4278 -794 translate0.490859 dup scale/pagenum 8 def/fname (/usr/local/share/doc/rfc/Mirrors/ftp.isi.edu/in-notes/rfc2616.txt) def/fdir (/usr/local/share/doc/rfc/Mirrors/ftp.isi.edu/in-notes/) def/ftail (rfc2616.txt) def% User defined strings:/fmodstr (Fri Jun 11 11:46:00 1999) def/pagenumstr (8) def/user_header_p true def/user_header_left_str (RFC2616) def/user_header_center_str (RFC.net) def/user_header_right_str (Page 8 of 177) def%%EndPageSetupdo_header5 751 M(RFC 2616 HTTP/1.1 June 1999) s5 712 M( method is to be applied. Messages are passed in a format similar to) s5 699 M( that used by Internet mail [9] as defined by the Multipurpose) s5 686 M( Internet Mail Extensions \(MIME\) [7].) s5 660 M( HTTP is also used as a generic protocol for communication between) s5 647 M( user agents and proxies/gateways to other Internet systems, including) s5 634 M( those supported by the SMTP [16], NNTP [13], FTP [18], Gopher [2],) s5 621 M( and WAIS [10] protocols. In this way, HTTP allows basic hypermedia) s5 608 M( access to resources available from diverse applications.) s5 582 M(1.2 Requirements) s5 556 M( The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",) s5 543 M( "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this) s5 530 M( document are to be interpreted as described in RFC 2119 [34].) s5 504 M( An implementation is not compliant if it fails to satisfy one or more) s5 491 M( of the MUST or REQUIRED level requirements for the protocols it) s5 478 M( implements. An implementation that satisfies all the MUST or REQUIRED) s5 465 M( level and all the SHOULD level requirements for its protocols is said) s5 452 M( to be "unconditionally compliant"; one that satisfies all the MUST) s5 439 M( level requirements but not all the SHOULD level requirements for its) s5 426 M( protocols is said to be "conditionally compliant.") s5 400 M(1.3 Terminology) s5 374 M( This specification uses a number of terms to refer to the roles) s5 361 M( played by participants in, and objects of, the HTTP communication.) s5 335 M( connection) s5 322 M( A transport layer virtual circuit established between two programs) s5 309 M( for the purpose of communication.) s5 283 M( message) s5 270 M( The basic unit of HTTP communication, consisting of a structured) s5 257 M( sequence of octets matching the syntax defined in section 4 and) s5 244 M( transmitted via the connection.) s5 218 M( request) s5 205 M( An HTTP request message, as defined in section 5.) s5 179 M( response) s5 166 M( An HTTP response message, as defined in section 6.) s5 49 M(Fielding, et al. Standards Track [Page 8]) s_R_RS%%Page: (9-12) 3%%BeginPageSetup_S24 818 translate%Page: (9) 9%BeginPageSetup_S% N-up sub-page 1/40 -392 translate0.490859 dup scale/pagenum 9 def/fname (/usr/local/share/doc/rfc/Mirrors/ftp.isi.edu/in-notes/rfc2616.txt) def/fdir (/usr/local/share/doc/rfc/Mirrors/ftp.isi.edu/in-notes/) def/ftail (rfc2616.txt) def% User defined strings:/fmodstr (Fri Jun 11 11:46:00 1999) def/pagenumstr (9) def/user_header_p true def/user_header_left_str (RFC2616) def/user_header_center_str (RFC.net) def/user_header_right_str (Page 9 of 177) def%%EndPageSetupdo_header5 751 M(RFC 2616 HTTP/1.1 June 1999) s5 712 M( resource) s5 699 M( A network data object or service that can be identified by a URI,) s5 686 M( as defined in section 3.2. Resources may be available in multiple) s5 673 M( representations \(e.g. multiple languages, data formats, size, and) s5 660 M( resolutions\) or vary in other ways.) s5 634 M( entity) s5 621 M( The information transferred as the payload of a request or) s5 608 M( response. An entity consists of metainformation in the form of) s5 595 M( entity-header fields and content in the form of an entity-body, as) s5 582 M( described in section 7.) s5 556 M( representation) s5 543 M( An entity included with a response that is subject to content) s5 530 M( negotiation, as described in section 12. There may exist multiple) s5 517 M( representations associated with a particular response status.) s5 491 M( content negotiation) s5 478 M( The mechanism for selecting the appropriate representation when) s5 465 M( servicing a request, as described in section 12. The) s5 452 M( representation of entities in any response can be negotiated) s5 439 M( \(including error responses\).) s5 413 M( variant) s5 400 M( A resource may have one, or more than one, representation\(s\)) s5 387 M( associated with it at any given instant. Each of these) s5 374 M( representations is termed a `varriant'. Use of the term `variant') s5 361 M( does not necessarily imply that the resource is subject to content) s5 348 M( negotiation.) s5 322 M( client) s5 309 M( A program that establishes connections for the purpose of sending) s5 296 M( requests.) s5 270 M( user agent) s5 257 M( The client which initiates a request. These are often browsers,) s5 244 M( editors, spiders \(web-traversing robots\), or other end user tools.) s5 218 M( server) s5 205 M( An application program that accepts connections in order to) s5 192 M( service requests by sending back responses. Any given program may) s5 179 M( be capable of being both a client and a server; our use of these) s5 166 M( terms refers only to the role being performed by the program for a) s5 153 M( particular connection, rather than to the program's capabilities) s5 140 M( in general. Likewise, any server may act as an origin server,) s5 127 M( proxy, gateway, or tunnel, switching behavior based on the nature) s5 114 M( of each request.) s5 49 M(Fielding, et al. Standards Track [Page 9]) s_R%Page: (10) 10%BeginPageSetup_S% N-up sub-page 2/4278 -392 translate0.490859 dup scale/pagenum 10 def/fname (/usr/local/share/doc/rfc/Mirrors/ftp.isi.edu/in-notes/rfc2616.txt) def/fdir (/usr/local/share/doc/rfc/Mirrors/ftp.isi.edu/in-notes/) def/ftail (rfc2616.txt) def% User defined strings:/fmodstr (Fri Jun 11 11:46:00 1999) def/pagenumstr (10) def/user_header_p true def/user_header_left_str (RFC2616) def/user_header_center_str (RFC.net) def/user_header_right_str (Page 10 of 177) def%%EndPageSetupdo_header5 751 M(RFC 2616 HTTP/1.1 June 1999) s5 712 M( origin server) s5 699 M( The server on which a given resource resides or is to be created.) s5 673 M( proxy) s5 660 M( An intermediary program which acts as both a server and a client) s5 647 M( for the purpose of making requests on behalf of other clients.) s5 634 M( Requests are serviced internally or by passing them on, with) s5 621 M( possible translation, to other servers. A proxy MUST implement) s5 608 M( both the client and server requirements of this specification. A) s5 595 M( "transparent proxy" is a proxy that does not modify the request or) s5 582 M( response beyond what is required for proxy authentication and) s5 569 M( identification. A "non-transparent proxy" is a proxy that modifies) s5 556 M( the request or response in order to provide some added service to) s5 543 M( the user agent, such as group annotation services, media type) s5 530 M( transformation, protocol reduction, or anonymity filtering. Except) s5 517 M( where either transparent or non-transparent behavior is explicitly) s5 504 M( stated, the HTTP proxy requirements apply to both types of) s5 491 M( proxies.) s5 465 M( gateway) s5 452 M( A server which acts as an intermediary for some other server.) s5 439 M( Unlike a proxy, a gateway receives requests as if it were the) s5 426 M( origin server for the requested resource; the requesting client) s5 413 M( may not be aware that it is communicating with a gateway.) s5 387 M( tunnel) s5 374 M( An intermediary program which is acting as a blind relay between) s5 361 M( two connections. Once active, a tunnel is not considered a party) s5 348 M( to the HTTP communication, though the tunnel may have been) s5 335 M( initiated by an HTTP request. The tunnel ceases to exist when both) s5 322 M( ends of the relayed connections are closed.) s5 296 M( cache) s5 283 M( A program's local store of response messages and the subsystem) s5 270 M( that controls its message storage, retrieval, and deletion. A) s5 257 M( cache stores cacheable responses in order to reduce the response) s5 244 M( time and network bandwidth consumption on future, equivalent) s5 231 M( requests. Any client or server may include a cache, though a cache) s5 218 M( cannot be used by a server that is acting as a tunnel.) s5 192 M( cacheable) s5 179 M( A response is cacheable if a cache is allowed to store a copy of) s5 166 M( the response message for use in answering subsequent requests. The) s5 153 M( rules for determining the cacheability of HTTP responses are) s5 140 M( defined in section 13. Even if a resource is cacheable, there may) s5 127 M( be additional constraints on whether a cache can use the cached) s5 114 M( copy for a particular request.) s5 49 M(Fielding, et al. Standards Track [Page 10]) s_R%Page: (11) 11%BeginPageSetup_S% N-up sub-page 3/40 -794 translate0.490859 dup scale/pagenum 11 def/fname (/usr/local/share/doc/rfc/Mirrors/ftp.isi.edu/in-notes/rfc2616.txt) def/fdir (/usr/local/share/doc/rfc/Mirrors/ftp.isi.edu/in-notes/) def/ftail (rfc2616.txt) def% User defined strings:/fmodstr (Fri Jun 11 11:46:00 1999) def/pagenumstr (11) def/user_header_p true def/user_header_left_str (RFC2616) def/user_header_center_str (RFC.net) def/user_header_right_str (Page 11 of 177) def%%EndPageSetupdo_header5 751 M(RFC 2616 HTTP/1.1 June 1999) s5 712 M( first-hand) s5 699 M( A response is first-hand if it comes directly and without) s5 686 M( unnecessary delay from the origin server, perhaps via one or more) s5 673 M⌨️ 快捷键说明
复制代码
Ctrl + C
搜索代码
Ctrl + F
全屏模式
F11
切换主题
Ctrl + Shift + D
显示快捷键
?
增大字号
Ctrl + =
减小字号
Ctrl + -