Hypertext Transfer Protocol -- HTTP/1 - W3

1 Fielding, et alStandards Track[Page 1]Network Working Group R. FieldingRequest for Comments: 2616 UC IrvineObsoletes: 2068 J. GettysCategory: Standards Track Compaq/W3C J. C. Mogul Compaq H.

2 Frystyk W3C/MIT L. Masinter Xerox P. Leach Microsoft T. Berners-Lee W3C/MIT June, 1999 Hypertext Transfer Protocol -- of this MemoThis document specifies an Internet standards track Protocol for the Internet community, and requests discussion andsuggestions for improvements.

3 Please refer to the current edition of the Internet Official Protocol Standards (STD1) for the standardization state and status of this Protocol . Distribution of this memo is NoticeCopyright (C) The Internet Society (1999). All Rights Hypertext Transfer Protocol ( http ) is an application-level Protocol for distributed, collaborative, hypermediainformation systems. It is a generic, stateless, Protocol which can be used for many tasks beyond its use forhypertext, such as name servers and distributed object management systems, through extension of its requestmethods, error codes and headers [47].

4 A feature of http is the typing and negotiation of data representation,allowing systems to be built independently of the data being has been in use by the World-Wide Web global information initiative since 1990. This specification definesthe Protocol referred to as , and is an update to RFC 2068 [33].RFC 2616 , 1999 Fielding, et alStandards Track[Page 2]Table of ContentsHYPERTEXT Transfer Protocol -- of this Memo ..1 Copyright ..1 Table of .. Operation ..102 Notational Conventions and Generic Grammar .. BNF .. Rules ..123 Protocol Parameters.

5 Version .. Resource URL .. Comparison .. Formats .. Date .. Seconds .. Sets .. Charset .. Codings .. Codings .. Transfer Coding .. Types .. and Text Defaults .. Tokens .. Values .. Tags .. Units ..214 http Message .. Headers .. Length .. Header Fields ..23 RFC 2616 , 1999 Fielding, et alStandards Track[Page 3]5 Request .. Resource Identified by a Request .. Header Fields ..266 Response .. Code and Reason Phrase .. Header .. Header Fields .. Body .. Length ..298 Connections .. Connections .. Operation .. Servers.

6 Transmission Requirements .. Connections and Flow Control .. Connections for Error Status Messages .. of the 100 (Continue) Status .. Behavior if Server Prematurely Closes Connection ..339 Method Definitions .. and Idempotent Methods .. Methods .. Methods ..3710 Status Code Definitions .. 1xx .. Switching Protocols .. 2xx .. OK .. Created .. Accepted .. Non-Authoritative Information .. No Reset Content .. Partial Content ..39 RFC 2616 , 1999 Fielding, et alStandards Track[Page 4] Multiple Moved Permanently .. Found .. See Other.

7 Not Modified .. Use (Unused) .. Temporary Redirect .. Error 4xx .. Bad Request .. Payment Required .. Not Found .. Method Not Allowed .. Not Acceptable .. Proxy Authentication Required .. Request Timeout .. Conflict .. Gone .. Length Required .. Precondition Request Entity Too Large .. Request-URI Too Long .. Unsupported Media Type .. Requested Range Not Expectation Failed .. Error 5xx .. Internal Server Error .. Not Implemented .. Bad Service Unavailable .. Gateway Timeout .. http Version Not Supported ..4511 Access Negotiation.

8 Negotiation ..4713 Caching in http .. Mechanisms .. User Agent Warnings .. to the Rules and Model .. Expiration .. Expiration .. Calculations .. 2616 , 1999 Fielding, et alStandards Track[Page 5] Expiration Values .. Multiple Model .. Dates .. Tag Cache Validators .. and Strong Validators .. for When to Use Entity Tags and Last-Modified Dates .. Conditionals .. Cacheability .. Responses From Caches .. and Hop-by-hop Headers .. Headers .. Headers .. Byte Ranges .. Negotiated Responses .. and Non-Shared Caches .. or Incomplete Response Cache Behavior.

9 Effects of GET and HEAD .. After Updates or Deletions .. Field Definitions .. is Cacheable .. May be Stored by Caches .. of the Basic Expiration Mechanism .. Revalidation and Reload Control Extensions .. Origin Server Operation ..80 RFC 2616 , 1999 Fielding, et alStandards Track[Page 6] .. Ranges .. Retrieval Requests ..9215 Security Considerations .. of Server Log Information .. of Sensitive Information .. Sensitive Information in URI s .. Issues Connected to Accept Headers .. Based On File and Path Headers and Issues.

10 Credentials and Idle and Caching .. of Service Attacks on .. Media Type message/ http and application/ http .. Media Type multipart/byteranges .. Applications .. Between http Entities and RFC 2045 to Canonical Form .. of Date Formats .. of Content-Encoding ..103 RFC 2616 , 1999 Fielding, et alStandards Track[Page 7] of Transfer -Encoding .. and Line Length Limitations .. with Previous Versions .. from .. with Persistent Connections .. from RFC Copyright ..10821 Index ..1091 PurposeThe Hypertext Transfer Protocol ( http ) is an application-level Protocol for distributed, collaborative, hypermediainformation systems.