《HypertextTransferProtocolHTTP》由会员分享，可在线阅读，更多相关《HypertextTransferProtocolHTTP（122页珍藏版）》请在金锄头文库上搜索。
1、INTERNET-DRAFTHTTP/1.1Wednesday, July 30, 1997HTTP Working Group R. FieldingINTERNET-DRAFT UC Irvine J. Gettys J. C. Mogul DEC H. Frystyk T. Berners-Lee MIT/LCSExpires January 30, 1998 July 30, 1997Hypertext Transfer Protocol - HTTP/1.1Status of this MemoThis document is an Internet-Draft. Internet-
2、Drafts are working documents of the Internet Engineering Task Force (IETF), its areas, and its working groups. Note that other groups may also distribute working documents as Internet-Drafts.Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or made o
3、bsolete by other documents at any time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as “work in progress”.To learn the current status of any Internet-Draft, please check the “1id-abstracts.txt” listing contained in the Internet-Drafts Shadow Directorie
4、s on ftp.is.co.za (Africa), (Europe), munnari.oz.au (Pacific Rim), (US East Coast), or ftp.isi.edu (US West Coast).Distribution of this document is unlimited. Please send comments to the HTTP working group at . Discussions of the working group are archived at . General discussions about HTTP and t
5、he applications which use HTTP should take place on the mailing list. IETF process demands this disclaimer on all drafts.Abstract The Hypertext Transfer Protocol (HTTP) is an application-level protocol for distributed, collaborative, hypermedia information systems. It is a generic, stateless, object
6、-oriented protocol which can be used for many tasks, such as name servers and distributed object management systems, through extension of its request methods. A feature of HTTP is the typing and negotiation of data representation, allowing systems to be built independently of the data being transfer
7、red.HTTP has been in use by the World-Wide Web global information initiative since 1990. This specification defines the protocol referred to as “HTTP/1.1”.The issues list for HTTP/1.1 can be found at: http:/www.w3.org/Protocols/HTTP/Issues/.This draft does not resolve all open issues in the HTTP/1.1
8、 specification requiring closure before HTTP/1.1 goes to draft standard. It does, however, close most of them, and note where in the document there are still significant issues under discussion. The best way to view this document is to get a copy of the Word 97 document found at: http:/www.w3.org/Pr
9、otocols/HTTP/1.1/diff-v11-RFC2068to08.doc; all issues are noted as comments in the source document, with hyperlinks to the Issues list.The most significant outstanding issue is OPTIONS; there is a separate internet draft on the topic that you should review NOT incorporated into this draft (though ed
10、itorial notes identify where changes may occur). This draft is draft-ietf-http-options-00.txt.Also an issue: AGE-CALCULATION; Roy Fielding has issued an ID on the topic; Jeff Mogul intends to issue a draft as well.The editorial group is very interested in feedback on the sample table of requirements
11、 in this draft (issue REQUIREMENTS, section 1.9). Is it useful? How could it be improved?Open or drafting issues not incorporated into this draft include: REDIRECTS, ENCODING-NOT-CONNEG, DATE_IF_MODIFIED, 403VS404, PUT-RANGE, HOST, AGE-CALCULATION, RE-AUTHENTICATION-REQUESTED, VARYIssues incorporate
12、d into this draft where there is still controversy are noted in bold italic with an editors note. These are issues: CONTENT-ENCODING, CACHING-CGI.Issues incorporated into this draft being working group last called are: AUTH-CHUNKED, RETRY-AFTER, PROXY-REDIRECTClosed issues incorporated into this dra
13、ft include: PROXY-AUTHORIZATION, PROXY-LENGTH, LANGUAGE-TAG, TSPECIALS, STATUS100, QZERO, RANGE-ERROR, CLARIFY-NO-CACHE, COMMENT, CONTENT-LOCATION, QUOTED-BACK, CACHE-CONTRA, CACHE-DIRECTIVE, BYTE-RANGE, LWS-DELIMITER, CRLF, MAX-AGE, 100DATE, DISPOSITION, CHUNKED, CACHING, WARNINGS, VERSION, PROXY-M
14、AXAGE, CHARSET-WILDCARD, PADDING, CONNECTION, RANGES, WARNING-8859, SHOULD-8859, X-BYTERANGES, MULTIPLE-TRANSFER-CODINGS, LINK_HEADER. Editorial issues still open include: CLEANUP, UTF-8, URL-SYNTAX, ENTITY, DOCKDIGEST, 1310_CACHE.Editorial issues closed include: ACCEPT-RANGES, KEEP-ALIVE, BNFNAME, KEYWORDS, RESPONSE-VERSION, XREF, COMMON-HEADERS, NO-CACHE, FIX-REF, PERSIST-CONFUSED, CONNECTION2, GMT-UTC, PROXY-FORWARD, REFER
