Hypertext Transfer Protocol -- HTTP/1.1

最新推荐文章于 2024-07-17 09:42:16 发布
最新推荐文章于 2024-07-17 09:42:16 发布
阅读量568 收藏
点赞数 1
原文链接：http://www.cnblogs.com/lexus/archive/2012/05/23/2514352.html
版权
Hypertext Transfer Protocol -- HTTP/1.1

Hypertext Transfer Protocol -- HTTP/1.1

Hypertext Transfer Protocol -- HTTP/1.1

Status of this Memo

This document specifies an Internet standards track protocol for the
Internet community, and requests discussion and suggestions for
improvements. Please refer to the current edition of the "Internet
Official Protocol Standards" (STD 1) for the standardization state
and status of this protocol. Distribution of this memo is unlimited.

Copyright Notice

Copyright (C) The Internet Society (1999). All Rights Reserved.

Abstract

The Hypertext Transfer Protocol (HTTP) is an application-level
protocol for distributed, collaborative, hypermedia information
systems. It is a generic, stateless, protocol which can be used for
many tasks beyond its use for hypertext, such as name servers and
distributed object management systems, through extension of its
request methods, error codes and headers [47]. A feature of HTTP is
the typing and negotiation of data representation, allowing systems
to be built independently of the data being transferred.

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", and is an update to RFC 2068 [33].

Table of Contents

  1. Introduction ... 1
    1. Purpose ... 1.1
    2. Requirements ... 1.2
    3. Terminology ... 1.3
    4. Overall Operation ... 1.4
  2. Notational Conventions and Generic Grammar ... 2
    1. Augmented BNF ... 2.1
    2. Basic Rules ... 2.2
  3. Protocol Parameters ... 3
    1. HTTP Version ... 3.1
    2. Uniform Resource Identifiers ... 3.2
      1. General Syntax ... 3.2.1
      2. http URL ... 3.2.2
      3. URI Comparison ... 3.2.3
    3. Date/Time Formats ... 3.3
      1. Full Date ... 3.3.1
      2. Delta Seconds ... 3.3.2
    4. Character Sets ... 3.4
      1. Missing Charset ... 3.4.1
    5. Content Codings ... 3.5
    6. Transfer Codings ... 3.6
      1. Chunked Transfer Coding ... 3.6.1
    7. Media Types ... 3.7
      1. Canonicalization and Text Defaults ... 3.7.1
      2. Multipart Types ... 3.7.2
    8. Product Tokens ... 3.8
    9. Quality Values ... 3.9
    10. Language Tags ... 3.10
    11. Entity Tags ... 3.11
    12. Range Units ... 3.12
  4. HTTP Message ... 4
    1. Message Types ... 4.1
    2. Message Headers ... 4.2
    3. Message Body ... 4.3
    4. Message Length ... 4.4
    5. General Header Fields ... 4.5
  5. Request ... 5
    1. Request-Line ... 5.1
      1. Method ... 5.1.1
      2. Request-URI ... 5.1.2
    2. The Resource Identified by a Request ... 5.2
    3. Request Header Fields ... 5.3
  6. Response ... 6
    1. Status-Line ... 6.1
      1. Status Code and Reason Phrase ... 6.1.1
    2. Response Header Fields ... 6.2
  7. Entity ... 7
    1. Entity Header Fields ... 7.1
    2. Entity Body ... 7.2
      1. Type ... 7.2.1
      2. Entity Length ... 7.2.2
  8. Connections ... 8
    1. Persistent Connections ... 8.1
      1. Purpose ... 8.1.1
      2. Overall Operation ... 8.1.2
      3. Proxy Servers ... 8.1.3
      4. Practical Considerations ... 8.1.4
    2. Message Transmission Requirements ... 8.2
      1. Persistent Connections and Flow Control ... 8.2.1
      2. Monitoring Connections for Error Status Messages ... 8.2.2
      3. Use of the 100 (Continue) Status ... 8.2.3
      4. Client Behavior if Server Prematurely Closes Connection ... 8.2.4
  9. Method Definitions ... 9
    1. Safe and Idempotent Methods ... 9.1
      1. Safe Methods ... 9.1.1
      2. Idempotent Methods ... 9.1.2
    2. OPTIONS ... 9.2
    3. GET ... 9.3
    4. HEAD ... 9.4
    5. POST ... 9.5
    6. PUT ... 9.6
    7. DELETE ... 9.7
    8. TRACE ... 9.8
    9. CONNECT ... 9.9
  10. Status Code Definitions ... 10
    1. Informational 1xx ... 10.1
      1. 100 Continue ... 10.1.1
      2. 101 Switching Protocols ... 10.1.2
    2. Successful 2xx ... 10.2
      1. 200 OK ... 10.2.1
      2. 201 Created ... 10.2.2
      3. 202 Accepted ... 10.2.3
      4. 203 Non-Authoritative Information ... 10.2.4
      5. 204 No Content ... 10.2.5
      6. 205 Reset Content ... 10.2.6
      7. 206 Partial Content ... 10.2.7
    3. Redirection 3xx ... 10.3
      1. 300 Multiple Choices ... 10.3.1
      2. 301 Moved Permanently ... 10.3.2
      3. 302 Found ... 10.3.3
      4. 303 See Other ... 10.3.4
      5. 304 Not Modified ... 10.3.5
      6. 305 Use Proxy ... 10.3.6
      7. 306 (Unused) ... 10.3.7
      8. 307 Temporary Redirect ... 10.3.8
    4. Client Error 4xx ... 10.4
      1. 400 Bad Request ... 10.4.1
      2. 401 Unauthorized ... 10.4.2
      3. 402 Payment Required ... 10.4.3
      4. 403 Forbidden ... 10.4.4
      5. 404 Not Found ... 10.4.5
      6. 405 Method Not Allowed ... 10.4.6
      7. 406 Not Acceptable ... 10.4.7
      8. 407 Proxy Authentication Required ... 10.4.8
      9. 408 Request Timeout ... 10.4.9
      10. 409 Conflict ... 10.4.10
      11. 410 Gone ... 10.4.11
      12. 411 Length Required ... 10.4.12
      13. 412 Precondition Failed ... 10.4.13
      14. 413 Request Entity Too Large ... 10.4.14
      15. 414 Request-URI Too Long ... 10.4.15
      16. 415 Unsupported Media Type ... 10.4.16
      17. 416 Requested Range Not Satisfiable ... 10.4.17
      18. 417 Expectation Failed ... 10.4.18
    5. Server Error 5xx ... 10.5
      1. 500 Internal Server Error ... 10.5.1
      2. 501 Not Implemented ... 10.5.2
      3. 502 Bad Gateway ... 10.5.3
      4. 503 Service Unavailable ... 10.5.4
      5. 504 Gateway Timeout ... 10.5.5
      6. 505 HTTP Version Not Supported ... 10.5.6
  11. Access Authentication ... 11
  12. Content Negotiation ... 12
    1. Server-driven Negotiation ... 12.1
    2. Agent-driven Negotiation ... 12.2
    3. Transparent Negotiation ... 12.3
  13. Caching in HTTP ... 13
    1. @@ missing
      1. Cache Correctness ... 13.1.1
      2. Warnings ... 13.1.2
      3. Cache-control Mechanisms ... 13.1.3
      4. Explicit User Agent Warnings ... 13.1.4
      5. Exceptions to the Rules and Warnings ... 13.1.5
      6. Client-controlled Behavior ... 13.1.6
    2. Expiration Model ... 13.2
      1. Server-Specified Expiration ... 13.2.1
      2. Heuristic Expiration ... 13.2.2
      3. Age Calculations ... 13.2.3
      4. Expiration Calculations ... 13.2.4
      5. Disambiguating Expiration Values ... 13.2.5
      6. Disambiguating Multiple Responses ... 13.2.6
    3. Validation Model ... 13.3
      1. Last-Modified Dates ... 13.3.1
      2. Entity Tag Cache Validators ... 13.3.2
      3. Weak and Strong Validators ... 13.3.3
      4. Rules for When to Use Entity Tags and Last-Modified Dates ... 13.3.4
      5. Non-validating Conditionals ... 13.3.5
    4. Response Cacheability ... 13.4
    5. Constructing Responses From Caches ... 13.5
      1. End-to-end and Hop-by-hop Headers ... 13.5.1
      2. Non-modifiable Headers ... 13.5.2
      3. Combining Headers ... 13.5.3
      4. Combining Byte Ranges ... 13.5.4
    6. Caching Negotiated Responses ... 13.6
    7. Shared and Non-Shared Caches ... 13.7
    8. Errors or Incomplete Response Cache Behavior ... 13.8
    9. Side Effects of GET and HEAD ... 13.9
    10. Invalidation After Updates or Deletions ... 13.10
    11. Write-Through Mandatory ... 13.11
    12. Cache Replacement ... 13.12
    13. History Lists ... 13.13
  14. Header Field Definitions ... 14
    1. Accept ... 14.1
    2. Accept-Charset ... 14.2
    3. Accept-Encoding ... 14.3
    4. Accept-Language ... 14.4
    5. Accept-Ranges ... 14.5
    6. Age ... 14.6
    7. Allow ... 14.7
    8. Authorization ... 14.8
    9. Cache-Control ... 14.9
      1. What is Cacheable ... 14.9.1
      2. What May be Stored by Caches ... 14.9.2
      3. Modifications of the Basic Expiration Mechanism ... 14.9.3
      4. Cache Revalidation and Reload Controls ... 14.9.4
      5. No-Transform Directive ... 14.9.5
      6. Cache Control Extensions ... 14.9.6
    10. Connection ... 14.10
    11. Content-Encoding ... 14.11
    12. Content-Language ... 14.12
    13. Content-Length ... 14.13
    14. Content-Location ... 14.14
    15. Content-MD5 ... 14.15
    16. Content-Range ... 14.16
    17. Content-Type ... 14.17
    18. Date ... 14.18
      1. Clockless Origin Server Operation ... 14.18.1
    19. ETag ... 14.19
    20. Expect ... 14.20
    21. Expires ... 14.21
    22. From ... 14.22
    23. Host ... 14.23
    24. If-Match ... 14.24
    25. If-Modified-Since ... 14.25
    26. If-None-Match ... 14.26
    27. If-Range ... 14.27
    28. If-Unmodified-Since ... 14.28
    29. Last-Modified ... 14.29
    30. Location ... 14.30
    31. Max-Forwards ... 14.31
    32. Pragma ... 14.32
    33. Proxy-Authenticate ... 14.33
    34. Proxy-Authorization ... 14.34
    35. Range ... 14.35
      1. Byte Ranges ... 14.35.1
      2. Range Retrieval Requests ... 14.35.2
    36. Referer ... 14.36
    37. Retry-After ... 14.37
    38. Server ... 14.38
    39. TE ... 14.39
    40. Trailer ... 14.40
    41. Transfer-Encoding ... 14.41
    42. Upgrade ... 14.42
    43. User-Agent ... 14.43
    44. Vary ... 14.44
    45. Via ... 14.45
    46. Warning ... 14.46
    47. WWW-Authenticate ... 14.47
  15. Security Considerations ... 15
    1. Personal Information ... 15.1
      1. Abuse of Server Log Information ... 15.1.1
      2. Transfer of Sensitive Information ... 15.1.2
      3. Encoding Sensitive Information in URI's ... 15.1.3
      4. Privacy Issues Connected to Accept Headers ... 15.1.4
    2. Attacks Based On File and Path Names ... 15.2
    3. DNS Spoofing ... 15.3
    4. Location Headers and Spoofing ... 15.4
    5. Content-Disposition Issues ... 15.5
    6. Authentication Credentials and Idle Clients ... 15.6
    7. Proxies and Caching ... 15.7
      1. Denial of Service Attacks on Proxies ... 15.7.1
  16. Acknowledgments ... 16
  17. References ... 17
  18. Authors' Addresses ... 18
  19. Appendices ... 19
    1. Internet Media Type message/http and application/http ... 19.1
    2. Internet Media Type multipart/byteranges ... 19.2
    3. Tolerant Applications ... 19.3
    4. Differences Between HTTP Entities and RFC 2045 Entities ... 19.4
      1. MIME-Version ... 19.4.1
      2. Conversion to Canonical Form ... 19.4.2
      3. Conversion of Date Formats ... 19.4.3
      4. Introduction of Content-Encoding ... 19.4.4
      5. No Content-Transfer-Encoding ... 19.4.5
      6. Introduction of Transfer-Encoding ... 19.4.6
      7. MHTML and Line Length Limitations ... 19.4.7
    5. Additional Features ... 19.5
      1. Content-Disposition ... 19.5.1
    6. Compatibility with Previous Versions ... 19.6
      1. Changes from HTTP/1 ... 19.6.1
      2. Compatibility with HTTP/1 ... 19.6.2
      3. Changes from RFC 2068 ... 19.6.3
  20. Index ... 20
  21. Full Copyright Statement ... 21
posted on 2012-05-23 10:31  lexus 阅读( ...) 评论( ...) 编辑 收藏

转载于:https://www.cnblogs.com/lexus/archive/2012/05/23/2514352.html

a13393665983
关注
[RFC2616-HTTP/1.1 超文本传输协议]（翻译）[Part 1]
PiPiQ_Blog的博客
02-15 3889
原文：RFC 2616 - Hypertext Transfer Protocol -- HTTP/1.1 (ietf.org) （因本篇RFC较长，将其分为几篇文章进行翻译） 超文本传输​​协议——HTTP/1.1 超文本传输​​协议 (HTTP) 是分布式、协作、超媒体信息系统的应用层协议。它是一种通用的、无状态的协议，通过扩展其请求方法、错误代码和标头 [47]，可用于超文本之外的许多任务，例如名称服务器和分布式对象管理系统。 HTTP 的一个特性是数据表示的类型化和协商，允许独立于正在传输的数
Hypertext Transfer Protocol -- HTTP/1.1 specification
03-02 182
Hypertext Transfer Protocol -- HTTP/1.1 specification Hypertext Transfer Protocol -- HTTP/1.1Hypertext Transfer Protocol -- HTTP/1.1S...
Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content
时代终结者
02-10 580
https://tools.ietf.org/html/rfc7231.html#section-7.1.4
HTTP超文本传输协议-HTTP/1.1中文版
学习........
09-01 1047
 
RFC 2616 Hypertext Transfer Protocol -- HTTP/1.1
07-17
**RFC 2616**，即《Hypertext Transfer Protocol -- HTTP/1.1》，是超文本传输协议HTTP/1.1的标准文档。该文档由一组作者（包括R. Fielding、J. Gettys、J. Mogul等人）共同完成，并于1999年6月发布。HTTP/1.1是一种...
RFC 2616 - Hypertext Transfer Protocol -- HTTP 1.1协议详细参考文档
09-29
RFC 2616 - Hypertext Transfer Protocol -- HTTP 1.1协议详细参考文档
RFC-2068(HTTP)
10-28
HTTP是Hyper Text Transfer Protocol（超文本传输协议）的缩写。它的发展是万维网协会（World Wide Web Consortium）和Internet工作小组IETF（Internet Engineering Task Force）合作的结果，（他们）最终发布了一...
Hypertext Transfer Protocol Version 2
06-12
HTTP/2（Hypertext Transfer Protocol Version 2）是互联网工程任务组（IETF）提出的一种用于优化HTTP（Hypertext Transfer Protocol）语义的协议，它被提议替代HTTP 1.1。HTTP/2在2015年由M. Belshe、R. Peon、M. ...
超文本传输​​协议 - HTTP / 1.1（Hypertext Transfer Protocol -- HTTP/1.1）之方法定义（Method Definitions）...
weixin_30877181的博客
12-16 139
9方法定义 下面定义了HTTP / 1.1的一组常用方法。尽管可以扩展这个集合，但是另外的方法不能假定为单独扩展的客户端和服务器共享相同的语义。 主机请求头域（14.23节）必须伴随所有的HTTP / 1.1请求。 9.1安全和幂等方法 9.1.1安全方法 实现者应该意识到，软件代表了用户在互联网上的交互，并且应该小心让用户意识到他们可能采取的任何可能对他们自己或他人意想不到的重要行为。...
HTTP协议（详解）
田螺姑娘的博客
07-03 5万+
HTTP协议：全称为Hyper Text Transfer Protocol（超文本传输协议）。HTTP协议是用于从（WWW：World Wide Web，简称万维网）服务器传输超文本到本地浏览器的传输协议。HTTP协议工作于B/S架构上，浏览器作为HTTP客户端通过URL向HTTP服务端即WEB服务端发送请求（Request）。Web服务端根据接收到的请求数据后，向客户端发送响应信息（Response）。HTTP协议是基于TCP/IP通信协议来传输数据。...
http与https详解
dvlinker的技术专栏
04-30 2万+
http与https详解
HTTP协议详解
qq15035899256的博客
08-02 5万+
本文是HTTP协议的学习，了解HTTP协议的工作过程，HTTP的请求和响应格式，以及如何手写HTTP服务器。之后的学习内容将持续更新！！！
HTTP 协议详解(史上最全)
最新发布
qqwangfan的专栏
07-17 7830
如果没有 Cookie，直接将要存储的数据保存在客户端浏览器所在的主机的硬盘上，那么就会出现很大的安全风险，比如当你不小心打开某个不安全的网站，该网站就可以在你的硬盘上写一个病毒程序，那么你的电脑就挂了！假设我用 bing 浏览器搜索蛋糕，会发现有的搜索结果带有广告字眼，这就相当于广告主在 bing 浏览器用来引流的，当该网站的点击次数越多，用户的成交量也就会上升，金主给浏览器的广告费也就增多。如果最终我们只需要付一件产品的钱，就是幂等的，如果要支付N件产品的钱，就不是幂等的。
RFC 2068 Hypertext Transfer Protocol -- HTTP/1.1
SAP攻城狮
05-21 7784
http://www.rfc-editor.org/rfc/rfc2616.txt This document specifies an Internet standards track protocol for the   Internet community, and requests discussion and suggestions for   improvements.  Pleas
HTTP协议格式详解（总结）
热门推荐
近未来
05-09 15万+
认识url url：就是我们平时说的“网址” HTTP协议格式 HTTP：请求响应机制 HTTP底层协议：TCP 协议 TCP 的特点：面向连接，保证可靠性 面向连接：我要和对应的服务器进行通信，第一件事情就是要把连接建立好 一个简单的网络通信： 建立连接 发请求 响应请求并断开连接 应用层核心工作： 把数据通过 TCP 实现从A点到B点，但是从A——>B只是最基础阶段，它后续要对HT...
超文本传输协议版本 2
WuOu的专栏
09-17 2720
超文本传输协议版本 2 IETF HTTP2草案(draft-ietf-httpbis-http2-13) 摘要 本规范描述了一种优化的超文本传输协议(HTTP)。HTTP/2通过引进报头字段压缩以及多路复用来更有效利用网络资源、减少感知延迟。另外还介绍了服务器推送规范。 本文档保持对HTTP/1.1的后向兼容，HTTP的现有的语义保持不变。 1 介绍
HTTP/1.1协议标准：Hypertext Transfer Protocol的应用与扩展
HTTP（Hypertext Transfer Protocol）是一种应用层协议，用于分布式、协作的超媒体信息系统。它是一个通用的、无状态的协议，可以用于许多超越超文本的任务，如名称服务器和分布式对象管理系统，通过扩展其请求方法...
评论
添加红包

请填写红包祝福语或标题

个

红包个数最小为10个

元

红包金额最低5元

当前余额3.43元 前往充值 >
需支付：10.00元
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付元
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明：

1.余额是钱包充值的虚拟货币，按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载，可以购买VIP、付费专栏及课程。

余额充值