📄 rfc1945.4up.ps
字号:
( additional capabilities of the sender. The <major> number is) s5 166 M( incremented when the format of a message within the protocol is) s5 153 M( changed.) s5 127 M( The version of an HTTP message is indicated by an HTTP-Version field) s5 114 M( in the first line of the message. If the protocol version is not) s5 101 M( specified, the recipient must assume that the message is in the) s5 49 M(Berners-Lee, et al Informational [Page 12]) s_R_RS%%Page: (13-16) 4%%BeginPageSetup_S24 818 translate%Page: (13) 13%BeginPageSetup_S% N-up sub-page 1/40 -392 translate0.490859 dup scale/pagenum 13 def/fname (/usr/local/share/doc/rfc/Mirrors/ftp.isi.edu/in-notes/rfc1945.txt) def/fdir (/usr/local/share/doc/rfc/Mirrors/ftp.isi.edu/in-notes/) def/ftail (rfc1945.txt) def% User defined strings:/fmodstr (Thu May 16 00:00:00 1996) def/pagenumstr (13) def/user_header_p true def/user_header_left_str (RFC1945) def/user_header_center_str (RFC.net) def/user_header_right_str (Page 13 of 61) def%%EndPageSetupdo_header5 751 M(RFC 1945 HTTP/1.0 May 1996) s5 712 M( simple HTTP/0.9 format.) s5 686 M( HTTP-Version = "HTTP" "/" 1*DIGIT "." 1*DIGIT) s5 660 M( Note that the major and minor numbers should be treated as separate) s5 647 M( integers and that each may be incremented higher than a single digit.) s5 634 M( Thus, HTTP/2.4 is a lower version than HTTP/2.13, which in turn is) s5 621 M( lower than HTTP/12.3. Leading zeros should be ignored by recipients) s5 608 M( and never generated by senders.) s5 582 M( This document defines both the 0.9 and 1.0 versions of the HTTP) s5 569 M( protocol. Applications sending Full-Request or Full-Response) s5 556 M( messages, as defined by this specification, must include an HTTP-) s5 543 M( Version of "HTTP/1.0".) s5 517 M( HTTP/1.0 servers must:) s5 491 M( o recognize the format of the Request-Line for HTTP/0.9 and) s5 478 M( HTTP/1.0 requests;) s5 452 M( o understand any valid request in the format of HTTP/0.9 or) s5 439 M( HTTP/1.0;) s5 413 M( o respond appropriately with a message in the same protocol) s5 400 M( version used by the client.) s5 374 M( HTTP/1.0 clients must:) s5 348 M( o recognize the format of the Status-Line for HTTP/1.0 responses;) s5 322 M( o understand any valid response in the format of HTTP/0.9 or) s5 309 M( HTTP/1.0.) s5 283 M( Proxy and gateway applications must be careful in forwarding requests) s5 270 M( that are received in a format different than that of the) s5 257 M( application's native HTTP version. Since the protocol version) s5 244 M( indicates the protocol capability of the sender, a proxy/gateway must) s5 231 M( never send a message with a version indicator which is greater than) s5 218 M( its native version; if a higher version request is received, the) s5 205 M( proxy/gateway must either downgrade the request version or respond) s5 192 M( with an error. Requests with a version lower than that of the) s5 179 M( application's native format may be upgraded before being forwarded;) s5 166 M( the proxy/gateway's response to that request must follow the server) s5 153 M( requirements listed above.) s5 49 M(Berners-Lee, et al Informational [Page 13]) s_R%Page: (14) 14%BeginPageSetup_S% N-up sub-page 2/4278 -392 translate0.490859 dup scale/pagenum 14 def/fname (/usr/local/share/doc/rfc/Mirrors/ftp.isi.edu/in-notes/rfc1945.txt) def/fdir (/usr/local/share/doc/rfc/Mirrors/ftp.isi.edu/in-notes/) def/ftail (rfc1945.txt) def% User defined strings:/fmodstr (Thu May 16 00:00:00 1996) def/pagenumstr (14) def/user_header_p true def/user_header_left_str (RFC1945) def/user_header_center_str (RFC.net) def/user_header_right_str (Page 14 of 61) def%%EndPageSetupdo_header5 751 M(RFC 1945 HTTP/1.0 May 1996) s5 712 M(3.2 Uniform Resource Identifiers) s5 686 M( URIs have been known by many names: WWW addresses, Universal Document) s5 673 M( Identifiers, Universal Resource Identifiers [2], and finally the) s5 660 M( combination of Uniform Resource Locators \(URL\) [4] and Names \(URN\)) s5 647 M( [16]. As far as HTTP is concerned, Uniform Resource Identifiers are) s5 634 M( simply formatted strings which identify--via name, location, or any) s5 621 M( other characteristic--a network resource.) s5 595 M(3.2.1 General Syntax) s5 569 M( URIs in HTTP can be represented in absolute form or relative to some) s5 556 M( known base URI [9], depending upon the context of their use. The two) s5 543 M( forms are differentiated by the fact that absolute URIs always begin) s5 530 M( with a scheme name followed by a colon.) s5 504 M( URI = \( absoluteURI | relativeURI \) [ "#" fragment ]) s5 478 M( absoluteURI = scheme ":" *\( uchar | reserved \)) s5 452 M( relativeURI = net_path | abs_path | rel_path) s5 426 M( net_path = "//" net_loc [ abs_path ]) s5 413 M( abs_path = "/" rel_path) s5 400 M( rel_path = [ path ] [ ";" params ] [ "?" query ]) s5 374 M( path = fsegment *\( "/" segment \)) s5 361 M( fsegment = 1*pchar) s5 348 M( segment = *pchar) s5 322 M( params = param *\( ";" param \)) s5 309 M( param = *\( pchar | "/" \)) s5 283 M( scheme = 1*\( ALPHA | DIGIT | "+" | "-" | "." \)) s5 270 M( net_loc = *\( pchar | ";" | "?" \)) s5 257 M( query = *\( uchar | reserved \)) s5 244 M( fragment = *\( uchar | reserved \)) s5 218 M( pchar = uchar | ":" | "@" | "&" | "=" | "+") s5 205 M( uchar = unreserved | escape) s5 192 M( unreserved = ALPHA | DIGIT | safe | extra | national) s5 166 M( escape = "%" HEX HEX) s5 153 M( reserved = ";" | "/" | "?" | ":" | "@" | "&" | "=" | "+") s5 140 M( extra = "!" | "*" | "'" | "\(" | "\)" | ",") s5 127 M( safe = "$" | "-" | "_" | ".") s5 114 M( unsafe = CTL | SP | <"> | "#" | "%" | "<" | ">") s5 101 M( national = <any OCTET excluding ALPHA, DIGIT,) s5 49 M(Berners-Lee, et al Informational [Page 14]) s_R%Page: (15) 15%BeginPageSetup_S% N-up sub-page 3/40 -794 translate0.490859 dup scale/pagenum 15 def/fname (/usr/local/share/doc/rfc/Mirrors/ftp.isi.edu/in-notes/rfc1945.txt) def/fdir (/usr/local/share/doc/rfc/Mirrors/ftp.isi.edu/in-notes/) def/ftail (rfc1945.txt) def% User defined strings:/fmodstr (Thu May 16 00:00:00 1996) def/pagenumstr (15) def/user_header_p true def/user_header_left_str (RFC1945) def/user_header_center_str (RFC.net) def/user_header_right_str (Page 15 of 61) def%%EndPageSetupdo_header5 751 M(RFC 1945 HTTP/1.0 May 1996) s5 712 M( reserved, extra, safe, and unsafe>) s5 686 M( For definitive information on URL syntax and semantics, see RFC 1738) s5 673 M( [4] and RFC 1808 [9]. The BNF above includes national characters not) s5 660 M( allowed in valid URLs as specified by RFC 1738, since HTTP servers) s5 647 M( are not restricted in the set of unreserved characters allowed to) s5 634 M( represent the rel_path part of addresses, and HTTP proxies may) s5 621 M( receive requests for URIs not defined by RFC 1738.) s5 595 M(3.2.2 http URL) s5 569 M( The "http" scheme is used to locate network resources via the HTTP) s5 556 M( protocol. This section defines the scheme-specific syntax and) s5 543 M( semantics for http URLs.) s5 517 M( http_URL = "http:" "//" host [ ":" port ] [ abs_path ]) s5 491 M( host = <A legal Internet host domain name) s5 478 M( or IP address \(in dotted-decimal form\),) s5 465 M( as defined by Section 2.1 of RFC 1123>) s5 439 M( port = *DIGIT) s5 413 M( If the port is empty or not given, port 80 is assumed. The semantics) s5 400 M( are that the identified resource is located at the server listening) s5 387 M( for TCP connections on that port of that host, and the Request-URI) s5 374 M( for the resource is abs_path. If the abs_path is not present in the) s5 361 M( URL, it must be given as "/" when used as a Request-URI \(Section) s5 348 M( 5.1.2\).) s5 322 M( Note: Although the HTTP protocol is independent of the transport) s5 309 M( layer protocol, the http URL only identifies resources by their) s5 296 M( TCP location, and thus non-TCP resources must be identified by) s5 283 M( some other URI scheme.) s5 257 M( The canonical form for "http" URLs is obtained by converting any) s5 244 M( UPALPHA characters in host to their LOALPHA equivalent \(hostnames are) s5 231 M( case-insensitive\), eliding the [ ":" port ] if the port is 80, and) s5 218 M( replacing an empty abs_path with "/".) s5 192 M(3.3 Date/Time Formats) s5 166 M( HTTP/1.0 applications have historically allowed three different) s5 153 M( formats for the representation of date/time stamps:) s5 127 M( Sun, 06 Nov 1994 08:49:37 GMT ; RFC 822, updated by RFC 1123) s5 114 M( Sunday, 06-Nov-94 08:49:37 GMT ; RFC 850, obsoleted by RFC 1036) s5 101 M( Sun Nov 6 08:49:37 1994 ; ANSI C's asctime\(\) format) s5 49 M(Berners-Lee, et al Informational [Page 15]) s_R%Page: (16) 16%BeginPageSetup_S% N-up sub-page 4/4278 -794 translate0.490859 dup scale/pagenum 16 def/fname (/usr/local/share/doc/rfc/Mirrors/ftp.isi.edu/in-notes/rfc1945.txt) def/fdir (/usr/local/share/doc/rfc/Mirrors/ftp.isi.edu/in-notes/) def/ftail (rfc1945.txt) def% User defined strings:/fmodstr (Thu May 16 00:00:00 1996) def/pagenumstr (16) def/user_header_p true def/user_header_left_str (RFC1945) def/user_header_center_str (RFC.net) def/user_header_right_str (Page 16 of 61) def%%EndPageSetupdo_header5 751 M(RFC 1945 HTTP/1.0 May 1996) s5 712 M( The first format is preferred as an Internet standard and represents) s5 699 M( a fixed-length subset of that defined by RFC 1123 [6] \(an update to) s5 686 M( RFC 822 [7]\). The second format is in common use, but is based on the) s5 673 M( obsolete RFC 850 [10] date format and lacks a four-digit year.) s5 660 M( HTTP/1.0 clients and servers that parse the date value should accept) s5 647 M( all three formats, though they must never generate the third) s5 634 M( \(asctime\) format.) s5 608 M( Note: Recipients of date values are encouraged to be robust in) s5 595 M( accepting date values that may have been generated by non-HTTP) s5 582 M( applications, as is sometimes the case when retrieving or posting) s5 569 M( messages via proxies/gateways to SMTP or NNTP.) s5 543 M( All HTTP/1.0 date/time stamps must be represented in Universal Time) s5 530 M( \(UT\), also known as Greenwich Mean Time \(GMT\), without exception.) s5 517 M( This is indicated in the first two formats by the inclusion of "GMT") s5 504 M( as the three-letter abbreviation for time zone, and should be assumed) s5 491 M( when reading the asctime format.) s5 465 M( HTTP-date = rfc1123-date | rfc850-date | asctime-date) s5 439 M( rfc1123-date = wkday "," SP date1 SP time SP "GMT") s5 426 M( rfc850-date = weekday "," SP date2 SP time SP "GMT") s5 413 M( asctime-date = wkday SP date3 SP time SP 4DIGIT) s5 387 M( date1 = 2DIGIT SP month SP 4DIGIT) s5 374 M( ; day month year \(e.g., 02 Jun 1982\)) s5 361 M( date2 = 2DIGIT "-" month "-" 2DIGIT) s5 348 M( ; day-month-year \(e.g., 02-Jun-82\)) s5 335 M( date3 = month SP \( 2DIGIT | \( SP 1DIGIT \)\)) s5 322 M( ; month day \(e.g., Jun 2\)) s5 296 M( time = 2DIGIT ":" 2DIGIT ":" 2DIGIT) s5 283 M( ; 00:00:00 - 23:59:59) s5 257 M( wkday = "Mon" | "Tue" | "Wed") s5 244 M( | "Thu" | "Fri" | "Sat" | "Sun") s5 218 M( weekday = "Monday" | "Tuesday" | "Wednesday") s5 205 M( | "Thursday" | "Friday" | "Saturday" | "Sunday") s5 179 M( month = "Jan" | "Feb" | "Mar" | "Apr") s5 166 M( | "May" | "Jun" | "Jul" | "Aug") s5 153 M( | "Sep" | "Oct" | "Nov" | "Dec") s5 127 M( Note: HTTP requirements for the date/time stamp format apply) s5 114 M( only to their usage within the protocol stream. Clients and) s5 101 M( servers are not required to use these formats for user) s5 49⌨️ 快捷键说明
复制代码
Ctrl + C
搜索代码
Ctrl + F
全屏模式
F11
切换主题
Ctrl + Shift + D
显示快捷键
?
增大字号
Ctrl + =
减小字号
Ctrl + -