超文本傳輸協議(HTTP)2 中英文對照版

IETF HTTP2草案(draft-ietf-httpbis-http2-13)





1 介紹

The Hypertext Transfer Protocol (HTTP) is a wildly successful protocol. However, the HTTP/1.1 message format ([RFC7230], Section 3) was designed to be implemented with the tools at hand in the 1990s, not modern Web application performance. As such it has several characteristics that have a negative overall effect on application performance today.

超文本傳輸協議(HTTP)是一個非常成功的協議。 但是HTTP/1.1 是針對90年代的情況而不是現代web應用的性能而設計的,導致它的一些特點已經對現代應用程序的性能產生負面影響。

In particular, HTTP/1.0 only allows one request to be outstanding at a time on a given connection. HTTP/1.1 pipelining only partially addressed request concurrency and suffers from head-of-line blocking. Therefore, clients that need to make many requests typically use multiple connections to a server in order to reduce latency.


Furthermore, HTTP/1.1 header fields are often repetitive and verbose, which, in addition to generating more or larger network packets, can cause the small initial TCP [TCP] congestion window to quickly fill. This can result in excessive latency when multiple requests are made on a single new TCP connection.


This specification addresses these issues by defining an optimized mapping of HTTP's semantics to an underlying connection. Specifically, it allows interleaving of request and response messages on the same connection and uses an efficient coding for HTTP header fields. It also allows prioritization of requests, letting more important requests complete more quickly, further improving performance.

本協議通過定義一個優化的基礎連接的HTTP語義映射來解決這些問題。 具體地,它允許在同一連接上交錯地建立請求和響應消息,並使用高效率編碼的HTTP報頭字段。 它還允許請求的優先級,讓更多的重要的請求更快速的完成,進一步提升了性能。

The resulting protocol is designed to be more friendly to the network, because fewer TCP connections can be used in comparison to HTTP/1.x. This means less competition with other flows, and longer-lived connections, which in turn leads to better utilization of available network capacity.

最終協議設計為對網絡更友好,因為它相對HTTP/1.x減少了TCP連接。 這意味著與其他流更少的競爭以及更長時間的連接,從而更有效地利用可用的網絡容量。

Finally, this encapsulation also enables more efficient processing of messages through use of binary message framing.


2 HTTP / 2協議概述

HTTP/2 provides an optimized transport for HTTP semantics. HTTP/2 supports all of the core features of HTTP/1.1, but aims to be more efficient in several ways.

HTTP/2 提供了HTTP語義的傳輸優化。HTTP/2支持所有HTTP/1.1的核心特徵,並且在不同的方面做的更高效。

The basic protocol unit in HTTP/2 is a frame (Section 4.1). Each frame type serves a different purpose. For example, HEADERS and DATA frames form the basis of HTTP requests and responses (Section 8.1); other frame types like SETTINGS, WINDOW_UPDATE, and PUSH_PROMISE are used in support of other HTTP/2 features.

HTTP/2中基本的協議單位是幀。每個幀都有不同的類型和用途。例如,報頭(HEADERS)和數據(DATA)幀組成了基本的HTTP 請求和響應;其他幀例如 設置(SETTINGS),窗口更新(WINDOW_UPDATE), 和推送承諾(PUSH_PROMISE)是用來實現HTTP/2的其他功能。

Multiplexing of requests is achieved by having each HTTP request-response exchanged assigned to a single stream (Section 5). Streams are largely independent of each other, so a blocked or stalled request does not prevent progress on other requests.


Flow control and prioritization ensure that it is possible to properly use multiplexed streams. Flow control (Section 5.2) helps to ensure that only data that can be used by a receiver is transmitted. Prioritization (Section 5.3) ensures that limited resources can be directed to the most important requests first.


HTTP/2 adds a new interaction mode, whereby a server can push responses to a client (Section 8.2). Server push allows a server to speculatively send a client data that the server anticipates the client will need, trading off some network usage against a potential latency gain. The server does this by synthesizing a request, which it sends as a PUSH_PROMISE frame. The server is then able to send a response to the synthetic request on a separate stream.


Frames that contain HTTP header fields are compressed (Section 4.3). HTTP requests can be highly redundant, so compression can reduce the size of requests and responses significantly.



The HTTP/2 specification is split into four parts:


  • Starting HTTP/2 (Section 3) covers how an HTTP/2 connection is initiated.
  • The framing (Section 4) and streams (Section 5) layers describe the way HTTP/2 frames are structured and formed into multiplexed streams.
  • Frame (Section 6) and error (Section 7) definitions include details of the frame and error types used in HTTP/2.
  • HTTP mappings (Section 8) and additional requirements (Section 9) describe how HTTP semantics are expressed using frames and streams.

  • 啟動HTTP/2(章節3)包含了一個HTTP/2連接是如何初始化的。

  • 幀(章節4)和流層(章節5)描述了 HTTP/2流的結構以及如何形成復用流的。
  • 幀(章節6)和錯誤碼(章節7)定義了HTTP/2中使用的流和錯誤類型的詳細內容。
  • HTTP尋址(章節8)和拓展需求(章節9)描述了HTTP語義化是如何由幀和流表達的。

While some of the frame and stream layer concepts are isolated from HTTP, the intent is not to define a completely generic framing layer. The framing and streams layers are tailored to the needs of the HTTP protocol and server push.



The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in RFC 2119 [RFC2119].

文檔中出現的關鍵字“必須”,“絕對不能”,“要求”,“應”,“不應”,“應該”,“不應該”,“建議”,“可以”及“可選”可通過在 RFC 2119 的解釋進行理解【RFC2119】

All numeric values are in network byte order. Values are unsigned unless otherwise indicated. Literal values are provided in decimal or hexadecimal as appropriate. Hexadecimal literals are prefixed with 0x to distinguish them from decimal literals.


The following terms are used:

  • client: The endpoint initiating the HTTP/2 connection. connection:A transport-level connection between two endpoints.
  • connection error: An error that affects the entire HTTP/2 connection.
  • endpoint: Either the client or server of the connection.
  • frame: The smallest unit of communication within an HTTP/2 connection, consisting of a header and a variable-length sequence of bytes structured according to the frame type.
  • peer: An endpoint. When discussing a particular endpoint, "peer" refers to the endpoint that is remote to the primary subject of discussion.
  • receiver: An endpoint that is receiving frames.
  • sender: An endpoint that is transmitting frames.
  • server: The endpoint which did not initiate the HTTP/2 connection.
  • stream: A bi-directional flow of frames across a virtual channel within the HTTP/2 connection.
  • stream error: An error on the individual HTTP/2 stream.


  • 客戶端:發起HTTP/2請求的端點
  • 連接:在兩個端點之間的傳輸層級別的連接
  • 連接錯誤:整個HTTP/2連接過程中發生的錯誤
  • 端點:連接的客戶端或服務器
  • 幀:HTTP/2.0通信連接中的最小單元,包括根據幀類型結構的字節的報頭和可變長度 的序列
  • 對等端:一個端點。當討論特定的端點時,“對等端”指的是討論的主題的遠程端點
  • 接收端:正在接收幀的端點
  • 發送端:正在傳輸幀的端點
  • 服務端:不是啟動HTTP/2連接的端點
  • 流:一個雙向字節幀流穿過HTTP/2連接中的虛擬通道
  • 流錯誤:一個HTTP/2流中的錯誤

3 啟動HTTP/2

An HTTP/2 connection is an application level protocol running on top of a TCP connection ([TCP]). The client is the TCP connection initiator.


HTTP/2 uses the same "http" and "https" URI schemes used by HTTP/1.1. HTTP/2 shares the same default port numbers: 80 for "http" URIs and 443 for "https" URIs. As a result, implementations processing requests for target resource URIs like http://example.org/foo or https://example.com/bar are required to first discover whether the upstream server (the immediate peer to which the client wishes to establish a connection) supports HTTP/2.

HTTP/2使用與HTTP/1.1相同的"http"和"https" 資源標識符(URI)。使用相同的默認端口:"http" 的80端口及“https”的443端口。因此,實現對例如http://example.org/foohttps://example.com/bar目標資源的URI請求處理需要首先確定上游服務端(當前客戶端希望建立連接的對等端)是否支持HTTP/2。

The means by which support for HTTP/2 is determined is different for "http" and "https" URIs. Discovery for "http" URIs is described in Section 3.2. Discovery for "https" URIs is described in Section 3.3.

這意味著檢測“http” 及“https” 的URIs是否支持HTTP/2的方法是不一樣的。檢測"http"URIs在章節3.2中描述。檢測"https"URIs 在章節3.3中描述。

3.1 HTTP/2版本定義

The protocol defined in this document has two identifiers.

  • The string "h2" identifies the protocol where HTTP/2 uses TLS [TLS12]. This identifier is used in the TLS application layer protocol negotiation extension (ALPN) [TLSALPN] field and any place that HTTP/2 over TLS is identified.

    The "h2" string is serialized into an ALPN protocol identifier as the two octet sequence: 0x68, 0x32.

  • The string "h2c" identifies the protocol where HTTP/2 is run over cleartext TCP. This identifier is used in the HTTP/1.1 Upgrade header field and any place that HTTP/2 over TCP is identified.


  • 字符"h2"表示HTTP/2協議使用TLS[TLS]。這種方式用在HTTP/1.1的升級字段、TLS 應用層協議協商擴展字段以及其他需要定義協議的地方。當在定義ALPN協議(序列化的字節)中序列化時。 "h2"字符序列化到 ALPN 協議中變成兩個字節序列:0x68,0x32。

  • 字符"h2c" 表示HTTP/2協議運行在明文TCP上。這個標識用在HTTP/1.1 升級報頭字段以及任何TCP是確定的地方。

Negotiating "h2" or "h2c" implies the use of the transport, security, framing and message semantics described in this document.

用到"h2" 或者 "h2c" 表明使用文檔中定義的傳輸、安全、幀及語義化消息。

Only implementations of the final, published RFC can identify themselves as "h2" or "h2c". Until such an RFC exists, implementations MUST NOT identify themselves using these strings.


Examples and text throughout the rest of this document use "h2" as a matter of editorial convenience only. Implementations of draft versions MUST NOT identify using this string.


Implementations of draft versions of the protocol MUST add the string "-" and the corresponding draft number to the identifier. For example, draft-ietf-httpbis-http2-11 over TLS is identified using the string "h2-11".

依據草案版本實現的協議必須添加字符"-"及相對應的草案版本進行標識。例如,基於TLS 的草案draft-ietf-httpbis-http2-11 需要使用字符"h2-11"進行標識。

Non-compatible experiments that are based on these draft versions MUST append the string "-" and an experiment name to the identifier. For example, an experimental implementation of packet mood-based encoding based on draft-ietf-httpbis-http2-09 might identify itself as "h2-09-emo". Note that any label MUST conform to the "token" syntax defined in Section 3.2.6 of [RFC7230]. Experimenters are encouraged to coordinate their experiments on the Email住址會使用灌水程式保護機制。你需要啟動Javascript才能觀看它 mailing list.

基於這些草案版本的不兼容的實驗必須在標識符中添加字符"-"及實驗名稱。例如,基於draft-ietf-httpbis-http2-09草案的情緒編碼實驗實現必須使用類似"h2-09-emo"的標識符。需要注意的是任何標籤必須符合[RFC7230]章節3.2.6 定義的"token"語法。鼓勵實驗者提交實驗到Email住址會使用灌水程式保護機制。你需要啟動Javascript才能觀看它 的郵件列表中。

3.2 Starting HTTP/2 for "http" URIs 針對"http"啟動HTTP/2

A client that makes a request to an "http" URI without prior knowledge about support for HTTP/2 uses the HTTP Upgrade mechanism (Section 6.7 of [RFC7230]). The client makes an HTTP/1.1 request that includes an Upgrade header field identifying HTTP/2 with the "h2c" token. The HTTP/1.1 request MUST include exactly one HTTP2-Settings (Section 3.2.1) header field.

客戶端無法預知服務端是否支持HTTP/2.0 的情況下使用HTTP升級機制發起“http” URI請求([RFC7230] 章節6.7)。客戶端發起一個http1.1請求,其中包含識別HTTP/2的升級報頭字段與h2c token。HTTP/1.1必須包含一個確切的HTTP2-Settings中的報頭字段。


GET /default.htm HTTP/1.1
Host: server.example.com
Connection: Upgrade, HTTP2-Settings
Upgrade: h2c
HTTP2-Settings: <base64url encoding of HTTP/2 SETTINGS payload>

Requests that contain an entity body MUST be sent in their entirety before the client can send HTTP/2 frames. This means that a large request entity can block the use of the connection until it is completely sent.


If concurrency of an initial request with subsequent requests is important, a small request can be used to perform the upgrade to HTTP/2, at the cost of an additional round-trip.


A server that does not support HTTP/2 can respond to the request as though the Upgrade header field were absent:


HTTP/1.1 200 OK
Content-Length: 243
Content-Type: text/html

A server MUST ignore a "h2" token in an Upgrade header field. Presence of a token with "h2" implies HTTP/2 over TLS, which is instead negotiated as described in Section 3.3.

服務端必須忽略升級報頭字段中的“h2” token。“h2” token基於TLS實現的HTTP/2,協商方法在章節3.3中定義。

A server that supports HTTP/2 can accept the upgrade with a 101 (Switching Protocols) response. After the empty line that terminates the 101 response, the server can begin sending HTTP/2 frames. These frames MUST include a response to the request that initiated the Upgrade.


HTTP/1.1 101 Switching Protocols
Connection: Upgrade
Upgrade: h2c

[ HTTP/2 connection ...

The first HTTP/2 frame sent by the server is a SETTINGS frame (Section 6.5). Upon receiving the 101 response, the client sends a connection preface (Section 3.5), which includes a SETTINGS frame.


The HTTP/1.1 request that is sent prior to upgrade is assigned stream identifier 1 and is assigned default priority values (Section 5.3.5). Stream 1 is implicitly half closed from the client toward the server, since the request is completed as an HTTP/1.1 request. After commencing the HTTP/2 connection, stream 1 is used for the response.

(*** 升級前所發送的HTTP/1.1請求被派送到標示流1並將賦予最高優先級。) HTTP/1.1最開始用來升級到2.0的請求用1來標示流並將賦予最高優先級。1流對發送到服務端的客戶端是隱式半封閉的,因為這個請求已經作為HTTP/1.1請求完成了。HTTP/2連接開始後, 1流在響應中使用。

3.2.1 HTTP2-Settings Header Field HTTP2-Setting報頭字段

A request that upgrades from HTTP/1.1 to HTTP/2 MUST include exactly one HTTP2-Settings header field. The HTTP2-Settings header field is a hop-by-hop header field that includes parameters that govern the HTTP/2 connection, provided in anticipation of the server accepting the request to upgrade.

從HTTP/1.1升級到HTTP/2的請求必須包含一個確切的HTTP2-Settings報頭字段。HTTP2-Settings 的報頭字段是逐跳報頭字段,它包含管理HTTP/2連接參數。這是從對於服務端接受升級請求的預測中所獲取的。

HTTP2-Settings    = token68

A server MUST reject an attempt to upgrade if this header field is not present. A server MUST NOT send this header field.


The content of the HTTP2-Settings header field is the payload of a SETTINGS frame (Section 6.5), encoded as a base64url string (that is, the URL- and filename-safe Base64 encoding described in Section 5 of [RFC4648], with any trailing '=' characters omitted). The ABNF [RFC5234] production for token68 is defined in Section 2.1 of [RFC7235].

HTTP2-Settings報頭字段的內容是設置(SETTINGS)幀的有效載體,使用base64url字符編碼(URL及文件名安全的Base64編碼,編碼描述在[RFC4648] 章節5中,忽略任何“=”字符。) ABNF[RFC5234]產品中對token68的定義在[RFC7235] 章節2.1中。

As a hop-by-hop header field, the Connection header field MUST include a value of HTTP2-Settings in addition to Upgrade when upgrading to HTTP/2.


A server decodes and interprets these values as it would any other SETTINGS frame. Acknowledgement of the SETTINGS parameters (Section 6.5.3) is not necessary, since a 101 response serves as implicit acknowledgment. Providing these values in the Upgrade request ensures that the protocol does not require default values for the above SETTINGS parameters, and gives a client an opportunity to provide other parameters prior to receiving any frames from the server.


3.3 Starting HTTP/2 for "https" URIs 針對“https”啟動HTTP/2

A client that makes a request to an "https" URI without prior knowledge about support for HTTP/2 uses TLS [TLS12] with the application layer protocol negotiation extension [TLSALPN].

客戶端在不瞭解服務端是否支持HTTP/2的時候,會使用TSL [TLS12] 於其應用層協議協商擴展 [TLSALPN]。

HTTP/2 over TLS uses the "h2" application token. The "h2c" token MUST NOT be sent by a client or selected by a server.

使用TLS的HTTP/2 使用"h2"程序token。“h2c”token絕對不能由客戶端或者選定的服務端發送。

Once TLS negotiation is complete, both the client and the server send a connection preface (Section 3.5).


3.4 Starting HTTP/2 with Prior Knowledge 先驗下啟動HTTP/2

A client can learn that a particular server supports HTTP/2 by other means. For example, [ALT-SVC] describes a mechanism for advertising this capability.


A client MAY immediately send HTTP/2 frames to a server that is known to support HTTP/2, after the connection preface (Section 3.5). A server can identify such a connection by the use of the "PRI" method in the connection preface. This only affects the establishment of HTTP/2 connections over cleartext TCP; implementations that support HTTP/2 over TLS MUST use protocol negotiation in TLS [TLSALPN].


Prior support for HTTP/2 is not a strong signal that a given server will support HTTP/2 for future connections. It is possible for server configurations to change; for configurations to differ between instances in clustered server; or network conditions to change.


3.5 HTTP/2 Connection Preface HTTP/2連接序言

Upon establishment of a TCP connection and determination that HTTP/2 will be used by both peers, each endpoint MUST send a connection preface as a final confirmation and to establish the initial SETTINGS parameters for the HTTP/2 connection.


The client connection preface starts with a sequence of 24 octets, which in hex notation are:



(the string PRI * HTTP/2.0\r\n\r\nSM\r\n\r\n). This sequence is followed by a SETTINGS frame (Section 6.5). The SETTINGS frame MAY be empty. The client sends the client connection preface immediately upon receipt of a 101 Switching Protocols response (indicating a successful upgrade), or as the first application data octets of a TLS connection. If starting an HTTP/2 connection with prior knowledge of server support for the protocol, the client connection preface is sent upon connection establishment.

(字符串PRI * HTTP/2.0\r\n\r\nSM\r\n\r\n)。這個序列後跟著一個設置幀,其可為空幀。客戶端在收到101轉換協議響應(升級成功指示)後馬上發送客戶端連接序言,或者作為TLS連接的第一個應用數據字節。如果在預先知道服務器支持HTTP/2的情況下啟動HTTP/2連接,客戶端連接序言在連接建立後發送。

The client connection preface is selected so that a large proportion of HTTP/1.1 or HTTP/1.0 servers and intermediaries do not attempt to process further frames. Note that this does not address the concerns raised in [TALKING].


The server connection preface consists of a potentially empty SETTINGS frame (Section 6.5) that MUST be the first frame the server sends in the HTTP/2 connection.


To avoid unnecessary latency, clients are permitted to send additional frames to the server immediately after sending the client connection preface, without waiting to receive the server connection preface. It is important to note, however, that the server connection preface SETTINGS frame might include parameters that necessarily alter how a client is expected to communicate with the server. Upon receiving the SETTINGS frame, the client is expected to honor any parameters established.


Clients and servers MUST terminate the TCP connection if either peer does not begin with a valid connection preface. A GOAWAY frame (Section 6.8) can be omitted if it is clear that the peer is not using HTTP/2.


4 HTTP Frames HTTP幀

Once the HTTP/2 connection is established, endpoints can begin exchanging frames.


4.1 Frame Format 幀格式

All frames begin with a fixed 8-octet header followed by a payload of between 0 and 16,383 octets.


  0                   1                   2                   3
  0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
 | R |     Length (14)           |   Type (8)    |   Flags (8)   |
 |R|                 Stream Identifier (31)                      |
 |                   Frame Payload (0...)                      ...

The fields of the frame header are defined as:

  • R :A reserved 2-bit field. The semantics of these bits are undefined and the bits MUST remain unset (0) when sending and MUST be ignored when receiving.
  • Length : The length of the frame payload expressed as an unsigned 14-bit integer. The 8 octets of the frame header are not included in this value.
  • Type : The 8-bit type of the frame. The frame type determines the format and semantics of the frame. Implementations MUST ignore and discard any frame that has a type that is unknown.
  • Flags :An 8-bit field reserved for frame-type specific boolean flags. Flags are assigned semantics specific to the indicated frame type. Flags that have no defined semantics for a particular frame type MUST be ignored, and MUST be left unset (0) when sending.
  • R: A reserved 1-bit field. The semantics of this bit are undefined and the bit MUST remain unset (0) when sending and MUST be ignored when receiving.
  • Stream Identifier: A 31-bit stream identifier (see Section 5.1.1). The value 0 is reserved for frames that are associated with the connection as a whole as opposed to an individual stream.


  • R : 保留的2位字段。這些字節的語義是未定義的,並且在發送的時候必須保持未設置(0),接收的時候必須被忽略此字段。
  • Length : 14位無符號整數的幀主體長度。8字節長度的幀報頭信息不計算在此內。
  • Type : 幀的8位類型。幀類型定義了剩餘的幀報頭和幀主體將如何被解釋。具體實現必須在收到未知幀類型(任何未在文檔中定義的幀)時作為連接錯誤中的類型協議錯誤(PROTOCOL_ERROR)處理。
  • Flags : 為幀類型保留的8字節字段有具體的布爾標識。 標識針對確定的幀類型賦予特定的語義。確定幀類型定義語義以外的標示必須被忽略,並且必須在發送的時候保留未設置(0)。
  • R : 1位的保留字段。這個字段的語義未設置並且必須在發送的時候保持未設置(0),在接受的時候必須被忽略。
  • Stream Identifier : 31字節的流標識符(見StreamIdentifiers)。0是保留的,標明幀是與連接相關作為一個整體而不是一個單獨的流。

The structure and content of the frame payload is dependent entirely on the frame type.


4.2 Frame Size 幀大小

The maximum size of a frame payload varies by frame type. The absolute maximum size of a frame payload is 214-1 (16,383) octets, meaning that the maximum frame size is 16,391 octets. All implementations MUST be capable of receiving and minimally processing frames up to this maximum size.

幀主體的最大長度限制因不同的幀類型而不同。最大幀主體的絕對長度是 $2^{14}-1$ (16,383)字節,表示最大的幀長度是16,391字節。所有的實現必須具備接收和處理此最大長度幀的能力。

Certain frame types, such as PING (Section 6.7), impose additional limits on the amount of payload data allowed.


If a frame size exceeds any defined limit, or is too small to contain mandatory frame data, the endpoint MUST send a FRAME_SIZE_ERROR error. A frame size error in a frame that could alter the state of the entire connection MUST be treated as a connection error (Section 5.4.1); this includes any frame carrying a header block (Section 4.3) (that is, HEADERS, PUSH_PROMISE, and CONTINUATION), SETTINGS, and any WINDOW_UPDATE frame with a stream identifier of 0.


4.3 Header Compression and Decompression 報頭壓縮和解壓縮

A header field in HTTP/2 is a name with one or more associated values. They are used within HTTP request and response messages as well as server push operations (see Section 8.2).


Header sets are collections of zero or more header fields. When transmitted over a connection, a header set is serialized into a header block using HTTP Header Compression [COMPRESSION]. The serialized header block is then divided into one or more octet sequences, called header block fragments, and transmitted within the payload of HEADERS (Section 6.2), PUSH_PROMISE (Section 6.6) or CONTINUATION (Section 6.10) frames.


HTTP Header Compression does not preserve the relative ordering of header fields. Header fields with multiple values are encoded into a single header field using a special delimiter (see Section, this preserves the relative order of values for that header field.

HTTP報文頭壓縮並不保留報頭字段的相關順序。具有多個值的報頭字段使用特定的分割器被編碼分割到一個單獨的報頭區域(見 章節8.1.2.3 HeaderOrdering),這保留了該報頭字段中各種值的對應順序。

The Cookie header field [COOKIE] is treated specially by the HTTP mapping (see Section


A receiving endpoint reassembles the header block by concatenating its fragments, then decompresses the block to reconstruct the header set.

A complete header block consists of either:

  • a single HEADERS or PUSH_PROMISE frame, with the END_HEADERS flag set, or
  • a HEADERS or PUSH_PROMISE frame with the END_HEADERS flag cleared and one or more CONTINUATION frames, where the last CONTINUATION frame has the END_HEADERS flag set.



  • 一個包含報頭終止標記集合的單獨的報頭HEADERS 或 推送承諾PUSH_PROMISE幀,或者
  • 一個報頭終止標記被清除的報頭HEADERS 或 推送承諾PUSH_PROMISE幀以及一個或多個延續CONTINUATION幀,最後一個延續CONTINUATION幀擁有報頭終止標記設置。

Header compression is stateful, using a single compression context for the entire connection. Each header block is processed as a discrete unit. Header blocks MUST be transmitted as a contiguous sequence of frames, with no interleaved frames of any other type or from any other stream. The last frame in a sequence of HEADERS or CONTINUATION frames MUST have the END_HEADERS flag set. The last frame in a sequence of PUSH_PROMISE or CONTINUATION frames MUST have the END_HEADERS flag set. This allows a header block to be logically equivalent to a single frame.


Header block fragments can only be sent as the payload of HEADERS, PUSH_PROMISE or CONTINUATION frames, because these frames carry data that can modify the compression context maintained by a receiver. An endpoint receiving HEADERS, PUSH_PROMISE or CONTINUATION frames MUST reassemble header blocks and perform decompression even if the frames are to be discarded. A receiver MUST terminate the connection with a connection error (Section 5.4.1) of type COMPRESSION_ERROR if it does not decompress a header block.


5 Streams and Multiplexing 流和多路復用

A "stream" is an independent, bi-directional sequence of frames exchanged between the client and server within an HTTP/2 connection. Streams have several important characteristics:

  • A single HTTP/2 connection can contain multiple concurrently open streams, with either endpoint interleaving frames from multiple streams.
  • Streams can be established and used unilaterally or shared by either the client or server.
  • Streams can be closed by either endpoint.
  • The order in which frames are sent on a stream is significant. Recipients process frames in the order they are received. In particular, the order of HEADERS, and DATA frames is semantically significant.
  • Streams are identified by an integer. Stream identifiers are assigned to streams by the endpoint initiating the stream.


  • 一個單獨的HTTP/2連接能夠保持多個同時打開的流,各個端點間從多個流中交換幀。
  • 流可以被被客戶端或者服務端單方面建立使用或分享。
  • 流可以被任何一個連接終端關閉。
  • 在流內發送幀的順序很重要。它們將按被接收的順序處理。特別是報頭及數據幀的順序語義上是有意義的。
  • 流以一個整數標識。標識符有啟動流的終端分配。

5.1 Stream States 流狀態

The lifecycle of a stream is shown in Figure 1.


                 PP    |        |    PP
              ,--------|  idle  |--------.
             /         |        |         \
            v          +--------+          v
     +----------+          |           +----------+
     |          |          | H         |          |
 ,---| reserved |          |           | reserved |---.
 |   | (local)  |          v           | (remote) |   |
 |   +----------+      +--------+      +----------+   |
 |      |          ES  |        |  ES          |      |
 |      | H    ,-------|  open  |-------.      | H    |
 |      |     /        |        |        \     |      |
 |      v    v         +--------+         v    v      |
 |   +----------+          |           +----------+   |
 |   |   half   |          |           |   half   |   |
 |   |  closed  |          | R         |  closed  |   |
 |   | (remote) |          |           | (local)  |   |
 |   +----------+          |           +----------+   |
 |        |                v                 |        |
 |        |  ES / R    +--------+  ES / R    |        |
 |        `----------->|        |<-----------'        |
 |  R                  | closed |                  R  |
 `-------------------->|        |<--------------------'

   H:  HEADERS frame (with implied CONTINUATIONs)
   PP: PUSH_PROMISE frame (with implied CONTINUATIONs)
   ES: END_STREAM flag
   R:  RST_STREAM frame

$$Figure 2: Stream States$$

Note that this diagram shows stream state transitions and frames that affect those transitions only. In this regard, CONTINUATION frames do not result in state transitions and are effectively part of the HEADERS or PUSH_PROMISE that they follow.


Both endpoints have a subjective view of the state of a stream that could be different when frames are in transit. Endpoints do not coordinate the creation of streams; they are created unilaterally by either endpoint. The negative consequences of a mismatch in states are limited to the "closed" state after sending RST_STREAM, where frames might be received for some time after closing.



Streams have the following states:

idle :

All streams start in the "idle" state. In this state, no frames have been exchanged.


The following transitions are valid from this state:

  • Sending or receiving a HEADERS frame causes the stream to become "open". The stream identifier is selected as described in Section 5.1.1. The same HEADERS frame can also cause a stream to immediately become "half closed".
  • Sending a PUSH_PROMISE frame marks the associated stream for later use. The stream state for the reserved stream transitions to "reserved (local)".
  • Receiving a PUSH_PROMISE frame marks the associated stream as reserved by the remote peer. The state of the stream becomes "reserved (remote)".


  • 發送或者接收一個報頭HEADERS幀導致流變成“打開”。流標識符如StreamIdentifiers說明。這個報頭HEADERS幀同樣可能導致流立即變成“半關閉”狀態。
  • 發送一個推送承諾PUSH_PROMISE幀標記相關的流後續再使用。保留流狀態將轉換為“保留(本地)”。
  • 接收一個推送承諾PUSH_PROMISE幀標記相關的流為遠程端點預留的流。這些流的狀態變成“保留(遠程)”

reserved (local) :

A stream in the "reserved (local)" state is one that has been promised by sending a PUSH_PROMISE frame. A PUSH_PROMISE frame reserves an idle stream by associating the stream with an open stream that was initiated by the remote peer (see Section 8.2).


In this state, only the following transitions are possible:

  • The endpoint can send a HEADERS frame. This causes the stream to open in a "half closed (remote)" state.
  • Either endpoint can send a RST_STREAM frame to cause the stream to become "closed". This releases the stream reservation.


  • 端點可以發送報頭HEADERS幀,致使流打開到“半封閉(遠程)”狀態。
  • 任意端點能發送一個RST_STREAM幀來使流變成“關閉”。這將釋放流的保留。

An endpoint MUST NOT send frames other than HEADERS or RST_STREAM in this state.


A PRIORITY frame MAY be received in this state. Receiving any frames other than RST_STREAM, or PRIORITY MUST be treated as a connection error (Section 5.4.1) of type PROTOCOL_ERROR.


reserved (remote) :

A stream in the "reserved (remote)" state has been reserved by a remote peer.


In this state, only the following transitions are possible:

  • Receiving a HEADERS frame causes the stream to transition to "half closed (local)".
  • Either endpoint can send a RST_STREAM frame to cause the stream to become "closed". This releases the stream reservation.


  • 接收一個報頭HEADERS幀並致使流轉換到“半封閉(本地)”狀態。
  • 任意一個端點能發送一個RST_STREAM 幀來使流變成“關閉”。這將釋放流的保留。

An endpoint MAY send a PRIORITY frame in this state to reprioritize the reserved stream. An endpoint MUST NOT send any other type of frame other than RST_STREAM or PRIORITY.

這種狀態下任意終端可以發送一個優先級PRIORITY幀來變更保留流的優先級順序。終端絕對不能發送任何RST_STREAM 和優先級PRIORITY以外的幀。

Receiving any other type of frame other than HEADERS or RST_STREAM MUST be treated as a connection error (Section 5.4.1) of type PROTOCOL_ERROR.

接收任何RST_STREAM 和優先級PRIORITY以外的幀必須作為類型為 協議錯誤PROTOCOL_ERROR的連接錯誤(章節5.4.1)來處理。

open :

A stream in the "open" state may be used by both peers to send frames of any type. In this state, sending peers observe advertised stream level flow control limits (Section 5.2).


From this state either endpoint can send a frame with an END_STREAM flag set, which causes the stream to transition into one of the "half closed" states: an endpoint sending an END_STREAM flag causes the stream state to become "half closed (local)"; an endpoint receiving an END_STREAM flag causes the stream state to become "half closed (remote)".


Either endpoint can send a RST_STREAM frame from this state, causing it to transition immediately to "closed".


half closed (local) :

A stream that is in the "half closed (local)" state cannot be used for sending frames. Only WINDOW_UPDATE, PRIORITY and RST_STREAM frames can be sent in this state.


A stream transitions from this state to "closed" when a frame that contains an END_STREAM flag is received, or when either peer sends a RST_STREAM frame.


A receiver can ignore WINDOW_UPDATE frames in this state, which might arrive for a short period after a frame bearing the END_STREAM flag is sent.


PRIORITY frames received in this state are used to reprioritize streams that depend on the current stream.


half closed (remote) :

A stream that is "half closed (remote)" is no longer being used by the peer to send frames. In this state, an endpoint is no longer obligated to maintain a receiver flow control window if it performs flow control.


If an endpoint receives additional frames for a stream that is in this state, other than WINDOW_UPDATE, PRIORITY or RST_STREAM, it MUST respond with a stream error (Section 5.4.2) of type STREAM_CLOSED.


A stream can transition from this state to "closed" by sending a frame that contains an END_STREAM flag, or when either peer sends a RST_STREAM frame.


closed :

The "closed" state is the terminal state.


An endpoint MUST NOT send frames on a closed stream. An endpoint that receives any frame other than PRIORITY after receiving a RST_STREAM MUST treat that as a stream error (Section 5.4.2) of type STREAM_CLOSED. Similarly, an endpoint that receives any frames after receiving a frame with the END_STREAM flag set MUST treat that as a connection error (Section 5.4.1) of type STREAM_CLOSED, unless the frame is permitted as described below.

終端絕對不能通過關閉的流發送幀。終端在收到RST_STREAM後接收的任何幀必須作為類型為流關閉STREAM_CLOSED的StreamErrorHandler流錯誤stream error(章節5.4.2)處理。相似的,終端接收到帶有END_STREAM標記設置的數據DATA幀之後的任何幀,或在帶有END_STREAM終止流標記且後面沒有延續CONTINUATION幀的報頭HEADERS幀之後收到任何幀都必須作為類型為流關閉STREAM_CLOSED的連接錯誤(章節5.4.1)處理。

WINDOW_UPDATE or RST_STREAM frames can be received in this state for a short period after a DATA or HEADERS frame containing an END_STREAM flag is sent. Until the remote peer receives and processes the frame bearing the END_STREAM flag, it might send frames of these types. Endpoints MUST ignore WINDOW_UPDATE or RST_STREAM frames received in this state, though endpoints MAY choose to treat frames that arrive a significant time after sending END_STREAM as a connection error (Section 5.4.1) of type PROTOCOL_ERROR.

在這種情況下,在帶有END_STREAM標記的DATA或HEADERS幀發送之後一小段時間內可以接收WINDOW_UPDATE或者RST_STREAM幀。在遠端對等端接收並處理帶有END_STREAM標記的幀之前,可以發送任意這幾種幀。在這種狀態下終端必須忽略接收到的WINDOW_UPDATE,PRIORITY, 或 RST_STREAM幀,但終端也可以當作類型為PROTOCOL_ERROR的連接錯誤(章節5.4.1)處理。

PRIORITY frames can be sent on closed streams to prioritize streams that are dependent on the closed stream. Endpoints SHOULD process PRIORITY frame, though they can be ignored if the stream has been removed from the dependency tree (see Section 5.3.4).


If this state is reached as a result of sending a RST_STREAM frame, the peer that receives the RST_STREAM might have already sent - or enqueued for sending - frames on the stream that cannot be withdrawn. An endpoint MUST ignore frames that it receives on closed streams after it has sent a RST_STREAM frame. An endpoint MAY choose to limit the period over which it ignores frames and treat frames that arrive after this time as being in error.


Flow controlled frames (i.e., DATA) received after sending RST_STREAM are counted toward the connection flow control window. Even though these frames might be ignored, because they are sent before the sender receives the RST_STREAM, the sender will consider the frames to count against the flow control window.


An endpoint might receive a PUSH_PROMISE frame after it sends RST_STREAM. PUSH_PROMISE causes a stream to become "reserved" even if the associated stream has been reset. Therefore, a RST_STREAM is needed to close an unwanted promised stream.


In the absence of more specific guidance elsewhere in this document, implementations SHOULD treat the receipt of a message that is not expressly permitted in the description of a state as a connection error (Section 5.4.1) of type PROTOCOL_ERROR.


5.1.1 Stream Identifiers 流標識

Streams are identified with an unsigned 31-bit integer. Streams initiated by a client MUST use odd-numbered stream identifiers; those initiated by the server MUST use even-numbered stream identifiers. A stream identifier of zero (0x0) is used for connection control messages; the stream identifier zero cannot be used to establish a new stream.


HTTP/1.1 requests that are upgraded to HTTP/2 (see Section 3.2) are responded to with a stream identifier of one (0x1). After the upgrade completes, stream 0x1 is "half closed (local)" to the client. Therefore, stream 0x1 cannot be selected as a new stream identifier by a client that upgrades from HTTP/1.1.


The identifier of a newly established stream MUST be numerically greater than all streams that the initiating endpoint has opened or reserved. This governs streams that are opened using a HEADERS frame and streams that are reserved using PUSH_PROMISE. An endpoint that receives an unexpected stream identifier MUST respond with a connection error (Section 5.4.1) of type PROTOCOL_ERROR.


The first use of a new stream identifier implicitly closes all streams in the "idle" state that might have been initiated by that peer with a lower-valued stream identifier. For example, if a client sends a HEADERS frame on stream 7 without ever sending a frame on stream 5, then stream 5 transitions to the "closed" state when the first frame for stream 7 is sent or received.


Stream identifiers cannot be reused. Long-lived connections can result in an endpoint exhausting the available range of stream identifiers. A client that is unable to establish a new stream identifier can establish a new connection for new streams. A server that is unable to establish a new stream identifier can send a GOAWAY frame so that the client is forced to open a new connection for new streams.


5.1.2 Stream Concurrency 流並發

A peer can limit the number of concurrently active streams using the SETTINGS_MAX_CONCURRENT_STREAMS parameter (see Section 6.5.2) within a SETTINGS frame. The maximum concurrent streams setting is specific to each endpoint and applies only to the peer that receives the setting. That is, clients specify the maximum number of concurrent streams the server can initiate, and servers specify the maximum number of concurrent streams the client can initiate.


Streams that are in the "open" state, or either of the "half closed" states count toward the maximum number of streams that an endpoint is permitted to open. Streams in any of these three states count toward the limit advertised in the SETTINGS_MAX_CONCURRENT_STREAMS setting. Streams in either of the "reserved" states do not count toward the stream limit.


Endpoints MUST NOT exceed the limit set by their peer. An endpoint that receives a HEADERS frame that causes their advertised concurrent stream limit to be exceeded MUST treat this as a stream error (Section 5.4.2). An endpoint that wishes to reduce the value of SETTINGS_MAX_CONCURRENT_STREAMS to a value that is below the current number of open streams can either close streams that exceed the new value or allow streams to complete.


5.2 Flow Control 流量控制

Using streams for multiplexing introduces contention over use of the TCP connection, resulting in blocked streams. A flow control scheme ensures that streams on the same connection do not destructively interfere with each other. Flow control is used for both individual streams and for the connection as a whole.


HTTP/2 provides for flow control through use of the WINDOW_UPDATE frame (Section 6.9).

HTTP/2 通過使用WINDOW_UPDATE幀類型來提供流量控制(章節6.9)。

5.2.1 Flow Control Principles 流量控制規則

HTTP/2 stream flow control aims to allow for future improvements to flow control algorithms without requiring protocol changes. Flow control in HTTP/2 has the following characteristics:

  1. Flow control is hop-by-hop, not end-to-end.
  2. Flow control is based on window update frames. Receivers advertise how many bytes they are prepared to receive on a stream and for the entire connection. This is a credit-based scheme.
  3. Flow control is directional with overall control provided by the receiver. A receiver MAY choose to set any window size that it desires for each stream and for the entire connection. A sender MUST respect flow control limits imposed by a receiver. Clients, servers and intermediaries all independently advertise their flow control window as a receiver and abide by the flow control limits set by their peer when sending.
  4. The initial value for the flow control window is 65,535 bytes for both new streams and the overall connection.
  5. The frame type determines whether flow control applies to a frame. Of the frames specified in this document, only DATA frames are subject to flow control; all other frame types do not consume space in the advertised flow control window. This ensures that important control frames are not blocked by flow control.
  6. Flow control cannot be disabled.
  7. HTTP/2 defines only the format and semantics of the WINDOW_UPDATE frame (Section 6.9). This document does not stipulate how a receiver decides when to send this frame or the value that it sends. Nor does it specify how a sender chooses to send packets. Implementations are able to select any algorithm that suits their needs.


  1. 流量控制是逐跳的,而不是頭尾連接的。
  2. 流量控制是基於窗口更新幀的。接收端廣播自己準備在流及整個連接過程中接收的字節大小。這是一個信用為基礎的方案。
  3. 流量控制是有方向性的,由接收端全權掌握。接收端可以選擇針對流及整個連接設置任意的窗口大小。發送端必須遵守接收端的流量控制限制。客戶端、服務端及中端代理作為接收者時都獨立的向外廣播他們各自的流量控制窗口,作為發送者時遵守接收端的限制。
  4. 每個新的流及整個連接的流量控制窗口初始值是65,535字節。
  5. 幀類型決定了是否適用流量控制規則。本文檔定義的幀中,只有DATA幀受流量控制;所有其他的幀不受廣播的流量控制窗口影響。這保證了重要的控制幀不因流量控制所阻塞。
  6. 流量控制不能被禁用。
  7. HTTP/2只標準化WINDOW_UPDATE幀格式(WINDOW_UPDATE)。它沒有規定接收端是何時發送幀或者發送什麼值,也沒有規定發送端如何選擇發送包。具體實現可以選擇任何滿足需求的算法。

Implementations are also responsible for managing how requests and responses are sent based on priority; choosing how to avoid head of line blocking for requests; and managing the creation of new streams. Algorithm choices for these could interact with any flow control algorithm.


5.2.2 Appropriate Use of Flow Control 正確使用流量控制

Flow control is defined to protect endpoints that are operating under resource constraints. For example, a proxy needs to share memory between many connections, and also might have a slow upstream connection and a fast downstream one. Flow control addresses cases where the receiver is unable process data on one stream, yet wants to continue to process other streams in the same connection.


Deployments that do not require this capability can advertise a flow control window of the maximum size, incrementing the available space when new data is received. This effectively disables flow control for that receiver. Conversely, a sender is always subject to the flow control window advertised by the receiver.


Deployments with constrained resources (for example, memory) can employ flow control to limit the amount of memory a peer can consume. Note, however, that this can lead to suboptimal use of available network resources if flow control is enabled without knowledge of the bandwidth-delay product (see [RFC1323]).

資源約束下(例如內存)的調度可以使用流量來限制一個對等端可以消耗的內存數量。需要注意的是如果在不知道帶寬延遲乘積的時候啟用流量控制可能導致無法最優的利用可用的網絡資源(see RFC1323)。

Even with full awareness of the current bandwidth-delay product, implementation of flow control can be difficult. When using flow control, the receiver MUST read from the TCP receive buffer in a timely fashion. Failure to do so could lead to a deadlock when critical frames, such as WINDOW_UPDATE, are not read and acted upon.


5.3 Stream priority 流優先級

A client can assign a priority for a new stream by including prioritization information in the HEADERS frame (Section 6.2) that opens the stream. For an existing stream, the PRIORITY frame (Section 6.3) can be used to change the priority.


The purpose of prioritization is to allow an endpoint to express how it would prefer its peer allocate resources when managing concurrent streams. Most importantly, priority can be used to select streams for transmitting frames when there is limited capacity for sending.


Explicitly setting the priority for a stream is input to a prioritization process. It does not guarantee any particular processing or transmission order for the stream relative to any other stream. An endpoint cannot force a peer to process concurrent streams in a particular order using priority. Expressing priority is therefore only ever a suggestion.


Prioritization information can be specified explicitly for streams as they are created using the HEADERS frame, or changed using the PRIORITY frame. Providing prioritization information is optional, so default values are used if no explicit indicator is provided (Section 5.3.5).


5.3.1 Stream Dependencies 流依賴

Each stream can be given an explicit dependency on another stream. Including a dependency expresses a preference to allocate resources to the identified stream rather than to the dependent stream.


A stream that is not dependent on any other stream is given a stream dependency of 0x0. In other words, the non-existent stream 0 forms the root of the tree.


A stream that depends on another stream is a dependent stream. The stream upon which a stream is dependent is a parent stream. A dependency on a stream that is not currently in the tree - such as a stream in the "idle" state - results in the stream being given a default priority (Section 5.3.5).

依賴其他流的流是一個有依賴流。被依賴的流是父節點流。被依賴的流如果當前不在依賴樹中——例如處於“空閒”狀態的流——流將會被賦予一個默認的優先級(章節 5.3.5)。

When assigning a dependency on another stream, the stream is added as a new dependency of the parent stream. Dependent streams that share the same parent are not order with respect to each other. For example, if streams B and C are dependent on stream A, and if stream D is created with a dependency on stream A, this results in a dependency order of A followed by B, C, and D in any order.


    A                 A
   / \      ==>      /|\
  B   C             B D C

$$Example of Default Dependency Creation$$

An exclusive flag allows for the insertion of a new level of dependencies. The exclusive flag causes the stream to become the sole dependency of its parent stream, causing other dependencies to become dependent on the prioritized stream. In the previous example, if stream D is created with an exclusive dependency on stream A, this results in D becoming the dependency parent of B and C.


    A                 |
   / \      ==>       D
  B   C              / \
                    B   C

$$Example of Exclusive Dependency Creation$$

Inside the dependency tree, a dependent stream SHOULD only be allocated resources if all of the streams that it depends on (the chain of parent streams up to 0x0) are either closed, or it is not possible to make progress on them.

在一個依賴樹中,一個有依賴的有應該只有在所有其依賴的父節點流(一直到流 0x0的所有父節點流)都關閉或者無法取得進展的情況下才能被分配資源。

A stream cannot depend on itself. An endpoint MUST treat this as a stream error (Section 5.4.2) of type PROTOCOL_ERROR.


5.3.2 Dependency Weighting 依賴權重

All dependent streams are allocated an integer weight between 1 to 256 (inclusive).


Streams with the same parent SHOULD be allocated resources proportionally based on their weight. Thus, if stream B depends on stream A with weight 4, and C depends on stream A with weight 12, and if no progress can be made on A, stream B ideally receives one third of the resources allocated to stream C.


5.3.3 Reprioritization 優先級重組

Stream priorities are changed using the PRIORITY frame. Setting a dependency causes a stream to become dependent on the identified parent stream.


Dependent streams move with their parent stream if the parent is reprioritized. Setting a dependency with the exclusive flag for a reprioritized stream moves all the dependencies of the new parent stream to become dependent on the reprioritized stream.


If a stream is made dependent on one of its own dependencies, the formerly dependent stream is first moved to be dependent on the reprioritized stream's previous parent. The moved dependency retains its weight.


For example, consider an original dependency tree where B and C depend on A, D and E depend on C, and F depends on D. If A is made dependent on D, then D takes the place of A. All other dependency relationships stay the same, except for F, which becomes dependent on A if the reprioritization is exclusive.


    ?                ?                ?                 ?
    |               / \               |                 |
    A              D   A              D                 D
   / \            /   / \            / \                |
  B   C     ==>  F   B   C   ==>    F   A       OR      A
     / \                 |             / \             /|\
    D   E                E            B   C           B C F
    |                                     |             |
    F                                     E             E
               (intermediate)   (non-exclusive)    (exclusive)

5.3.4 Prioritization State Management 優先級狀態管理

When a stream is removed from the dependency tree, its dependencies can be moved to become dependent on the parent of the closed stream. The weights of new dependencies are recalculated by distributing the weight of the dependency of the closed stream proportionally based on the weights of its dependencies.


Streams that are removed from the dependency tree cause some prioritization information to be lost. Resources are shared between streams with the same parent stream, which means that if a stream in that set closes or becomes blocked, any spare capacity allocated to a stream is distributed to the immediate neighbors of the stream. However, if the common dependency is removed from the tree, those streams share resources with streams at the next highest level.


For example, assume streams A and B share a parent, and streams C and D both depend on stream A. Prior to the removal of stream A, if streams A and D are unable to proceed, then stream C receives all the resources dedicated to stream A. If stream A is removed from the tree, the weight of stream A is divided between streams C and D. If stream D is still unable to proceed, this results in stream C receiving a reduced proportion of resources. For equal starting weights, C receives one third, rather than one half, of available resources.


It is possible for a stream to become closed while prioritization information that creates a dependency on that stream is in transit. If a stream identified in a dependency has had any associated priority information destroyed, then the dependent stream is instead assigned a default priority. This potentially creates suboptimal prioritization, since the stream could be given a priority that is higher than intended.


To avoid these problems, an endpoint SHOULD retain stream prioritization state for a period after streams become closed. The longer state is retained, the lower the chance that streams are assigned incorrect or default priority values.


This could create a large state burden for an endpoint, so this state MAY be limited. An endpoint MAY apply a fixed upper limit on the number of closed streams for which prioritization state is tracked to limit state exposure. The amount of additional state an endpoint maintains could be dependent on load; under high load, prioritization state can be discarded to limit resource commitments. In extreme cases, an endpoint could even discard prioritization state for active or reserved streams. If a fixed limit is applied, endpoints SHOULD maintain state for at least as many streams as allowed by their setting for SETTINGS_MAX_CONCURRENT_STREAMS.


An endpoint receiving a PRIORITY frame that changes the priority of a closed stream SHOULD alter the dependencies of the streams that depend on it, if it has retained enough state to do so.


5.4 Error Handling 錯誤處理

HTTP/2 framing permits two classes of error:

  • An error condition that renders the entire connection unusable is a connection error.
  • An error in an individual stream is a stream error.

A list of error codes is included in Section 7.


  • 使整個連接不可用的錯誤。
  • 單個流中出現的錯誤。


5.4.1 Connection Error Handling 連接錯誤處理

A connection error is any error which prevents further processing of the framing layer, or which corrupts any connection state.


An endpoint that encounters a connection error SHOULD first send a GOAWAY frame (Section 6.8) with the stream identifier of the last stream that it successfully received from its peer. The GOAWAY frame includes an error code that indicates why the connection is terminating. After sending the GOAWAY frame, the endpoint MUST close the TCP connection.


It is possible that the GOAWAY will not be reliably received by the receiving endpoint. In the event of a connection error, GOAWAY only provides a best effort attempt to communicate with the peer about why the connection is being terminated.


An endpoint can end a connection at any time. In particular, an endpoint MAY choose to treat a stream error as a connection error. Endpoints SHOULD send a GOAWAY frame when ending a connection, providing that circumstances permit it.


5.4.2 Stream Error Handling 流錯誤處理

A stream error is an error related to a specific stream that does not affect processing of other streams.


An endpoint that detects a stream error sends a RST_STREAM frame (Section 6.4) that contains the stream identifier of the stream where the error occurred. The RST_STREAM frame includes an error code that indicates the type of error.


A RST_STREAM is the last frame that an endpoint can send on a stream. The peer that sends the RST_STREAM frame MUST be prepared to receive any frames that were sent or enqueued for sending by the remote peer. These frames can be ignored, except where they modify connection state (such as the state maintained for header compression (Section 4.3), or flow control).


Normally, an endpoint SHOULD NOT send more than one RST_STREAM frame for any stream. However, an endpoint MAY send additional RST_STREAM frames if it receives frames on a closed stream after more than a round-trip time. This behavior is permitted to deal with misbehaving implementations.


An endpoint MUST NOT send a RST_STREAM in response to an RST_STREAM frame, to avoid looping.


5.4.3 Connection Termination 連接終止

If the TCP connection is torn down while streams remain in open or half closed states, then the endpoint MUST assume that those streams were abnormally interrupted and could be incomplete.


5.5 Extending HTTP/2 HTTP/2擴展

HTTP/2 permits extension of the protocol. Protocol extensions can be used to provide additional services or alter any aspect of the protocol, within the limitations described in this section. Extensions are effective only within the scope of a single HTTP/2 connection.


Extensions are permitted to use new frame types (Section 4.1), new settings (Section 6.5.2), new error codes (Section 7), or new header fields that start with a colon (:). Of these, registries are established for frame types (Section 11.2), settings (Section 11.3) and error codes (Section 11.4).


Implementations MUST ignore unknown or unsupported values in all extensible protocol elements. Implementations MUST discard frames that have unknown or unsupported types. This means that any of these extension points can be safely used by extensions without prior arrangement or negotiation.


However, extensions that could change the semantics of existing protocol components MUST be negotiated before being used. For example, an extension that changes the layout of the HEADERS frame cannot be used until the peer has given a positive signal that this is acceptable. In this case, it could also be necessary to coordinate when the revised layout comes into effect. Note that treating any frame other than DATA frames as flow controlled is such a change in semantics, and can only be done through negotiation.


This document doesn't mandate a specific method for negotiating the use of an extension, but notes that a setting (Section 6.5.2) could be used for that purpose. If both peers set a value that indicates willingness to use the extension, then the extension can be used. If a setting is used for extension negotiation, the initial value MUST be defined so that the extension is initially disabled.


6 Frame Definitions 幀定義

This specification defines a number of frame types, each identified by a unique 8-bit type code. Each frame type serves a distinct purpose either in the establishment and management of the connection as a whole, or of individual streams.


The transmission of specific frame types can alter the state of a connection. If endpoints fail to maintain a synchronized view of the connection state, successful communication within the connection will no longer be possible. Therefore, it is important that endpoints have a shared comprehension of how the state is affected by the use any given frame.


6.1 DATA 數據幀

DATA frames (type=0x0) convey arbitrary, variable-length sequences of octets associated with a stream. One or more DATA frames are used, for instance, to carry HTTP request or response payloads.


DATA frames MAY also contain arbitrary padding. Padding can be added to DATA frames to obscure the size of messages.


 0                   1                   2                   3
 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
 | [Pad High(8)] | [Pad Low (8)] |          Data (*)             .
 .                            Data (*)                         ...
 |                           Padding (*)                       ...

The DATA frame contains the following fields:

  • Pad Length:An 8-bit field containing the length of the frame padding in units of octets. This field is optional and is only present if the PADDED flag is set.
  • Data:Application data. The amount of data is the remainder of the frame payload after subtracting the length of the other fields that are present.
  • Padding:Padding octets that contain no application semantic value. Padding octets MUST be set to zero when sending and ignored when receiving.


  • Pad Length : 包含字節為單位的幀填充長度的8位字段。這個字段是可選的,並且只在設置了PADDED標記的情況下呈現。
  • Data : 應用數據。數據量的大小是幀的有效載荷減去其他呈現字段的長度。
  • Padding : 填充字節不包含任何應用語義值。天聰字節必須在發送的時候設置為0,在接收的時候忽略。

The DATA frame defines the following flags:

  • END_STREAM (0x1):Bit 1 being set indicates that this frame is the last that the endpoint will send for the identified stream. Setting this flag causes the stream to enter one of the "half closed" states or the "closed" state (Section 5.1).
  • END_SEGMENT (0x2):Bit 2 being set indicates that this frame is the last for the current segment. Intermediaries MUST NOT coalesce frames across a segment boundary and MUST preserve segment boundaries when forwarding frames.
  • PADDED (0x8):Bit 4 being set indicates that the Pad Length field is present.


  • END_STREAM (0x1) : 位1用來表示當前幀是確定的流發送的最後一幀。設置這個標記時流進入到一種半封閉狀態或者關閉狀態(章節5.1)。
  • END_SEGMENT (0x2) : 位2表示是當前端的最後一幀。代理端絕對不能跨越多個端的邊界來合併幀,轉發幀的時候代理端必須保持片段的邊界。
  • PADDED (0x8) : 位4用來表示Pad Length 字段是可見的。

DATA frames MUST be associated with a stream. If a DATA frame is received whose stream identifier field is 0x0, the recipient MUST respond with a connection error (Section 5.4.1) of type PROTOCOL_ERROR.


DATA frames are subject to flow control and can only be sent when a stream is in the "open" or "half closed (remote)" states. The entire DATA frame payload is included in flow control, including Pad Length and Padding fields if present. If a DATA frame is received whose stream is not in "open" or "half closed (local)" state, the recipient MUST respond with a stream error (Section 5.4.2) of type STREAM_CLOSED.


The total number of padding octets is determined by the value of the Pad Length field. If the length of the padding is greater than the length of the remainder of the frame payload, the recipient MUST treat this as a connection error (Section 5.4.1) of type PROTOCOL_ERROR.

填充字節的總數取決於Pad Length 的值。如果填充物的大小大於幀有效載荷的大小,接收端必須作為類型為協議錯誤的連接錯誤(章節5.4.1)處理。

Note: A frame can be increased in size by one octet by including a Pad Length field with a value of zero.

請注意 : 為幀的大小加1字節可通過增加一個值為0的Pad Length 值的方法。

Use of padding is a security feature; as such, its use demands some care, see Section 10.7.


6.2 HEADERS 報頭

The HEADERS frame (type=0x1) carries name-value pairs. It is used to open a stream (Section 5.1). HEADERS frames can be sent on a stream in the "open" or "half closed (remote)" states.


  0                   1                   2                   3
  0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
 |Pad Length? (8)|
 |E|                 Stream Dependency? (31)                     |
 |  Weight? (8)  |
 |                   Header Block Fragment (*)                 ...
 |                           Padding (*)                       ...

The HEADERS frame payload has the following fields:

  • Pad Length:An 8-bit field containing the length of the frame padding in units of octets. This field is optional and is only present if the PADDED flag is set.
  • E:A single bit flag indicates that the stream dependency is exclusive, see Section 5.3. This field is optional and is only present if the PRIORITY flag is set.
  • Stream Dependency:A 31-bit stream identifier for the stream that this stream depends on, see Section 5.3. This field is optional and is only present if the PRIORITY flag is set.
  • Weight:An 8-bit weight for the stream, see Section 5.3. Add one to the value to obtain a weight between 1 and 256. This field is optional and is only present if the PRIORITY flag is set.
  • Header Block Fragment:A header block fragment (Section 4.3).
  • Padding:Padding octets.


  • Pad Length : 8位的包含單位為字節幀填充長度字段。這個字段是可選的並只有在設置了PADDED 標記的情況下才呈現。
  • E : 1位的標記用於標識流依賴是否是專用的,見章節5.3。這個字段是可選的,並且只在優先級標記設置的情況下才呈現。
  • Stream Dependency : 31位流所依賴的流的標識符的字段,見章節5.3。這個字段是可選的,並且只在優先級標記設置的情況下才呈現。
  • Weight : 流的8位權重標記,見章節5.3。添加一個1-256的值來存儲流的權重。這個字段是可選的,並且只在優先級標記設置的情況下才呈現。
  • Header Block Fragment : 報頭塊碎片。
  • Padding : 填充字節

The HEADERS frame defines the following flags:

  • END_STREAM (0x1):Bit 1 being set indicates that the header block (Section 4.3) is the last that the endpoint will send for the identified stream. Setting this flag causes the stream to enter one of "half closed" states (Section 5.1).
  • A HEADERS frame that is followed by CONTINUATION frames carries the END_STREAM flag that signals the end of a stream. A CONTINUATION frame cannot be used to terminate a stream.
  • END_SEGMENT (0x2):Bit 2 being set indicates that this frame is the last for the current segment. Intermediaries MUST NOT coalesce frames across a segment boundary and MUST preserve segment boundaries when forwarding frames. END_SEGMENT, like END_STREAM, applies to a complete sequence of HEADERS and CONTINUATION frames.
  • END_HEADERS (0x4):Bit 3 being set indicates that this frame contains an entire header block (Section 4.3) and is not followed by any CONTINUATION frames. A HEADERS frame without the END_HEADERS flag set MUST be followed by a CONTINUATION frame for the same stream. A receiver MUST treat the receipt of any other type of frame or a frame on a different stream as a connection error (Section 5.4.1) of type PROTOCOL_ERROR.
  • PADDED (0x8):Bit 4 being set indicates that the Pad Length field is present.
  • PRIORITY (0x20):Bit 6 being set indicates that the Exclusive Flag (E), Stream Dependency, and Weight fields are present; see Section 5.3.


  • END_STREAM (0x1) : 位1用來標識這是發送端對確定的流發送的最後報頭區塊(章節4.3)。設置這個標記將使流進入一種半封閉狀態(章節5.1)。 後面伴隨帶有END_STREAM標記的延續幀的報頭幀表示流的終止。延續幀不用來用終止流。
  • END_SEGMENT (0x2) : 位2表示這是當前端的最後一幀。中介端絕對不能跨片段來合併幀,且在轉發幀的時候必須保持片段的邊界。
  • END_HEADERS (0x4) : 位3表示幀包含了整個的報頭塊(章節4.3),且後面沒有延續幀。 不帶有END_HEADERS標記的報頭幀在同個流上後面必須跟著延續幀。接收端接收到任何其他類型的幀或者在其他流上的幀必須作為類型為協議錯誤的連接錯誤處理。
  • PADDED (0x8) : 位4表示Pad Length字段會呈現。
  • PRIORITY (0x8) : 位6設置指示專用標記(E),流依賴及權重字段將會呈現;見章節5.3

The payload of a HEADERS frame contains a header block fragment (Section 4.3). A header block that does not fit within a HEADERS frame is continued in a CONTINUATION frame (Section 6.10).


HEADERS frames MUST be associated with a stream. If a HEADERS frame is received whose stream identifier field is 0x0, the recipient MUST respond with a connection error (Section 5.4.1) of type PROTOCOL_ERROR.


The HEADERS frame changes the connection state as described in Section 4.3.


The HEADERS frame includes optional padding. Padding fields and flags are identical to those defined for DATA frames (Section 6.1).


6.3 PRIORITY 優先級幀

The PRIORITY frame (type=0x2) specifies the sender-advised priority of a stream (Section 5.3). It can be sent at any time for an existing stream, including closed streams. This enables reprioritization of existing streams.


  0                   1                   2                   3
  0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
 |E|                  Stream Dependency (31)                     |
 |   Weight (8)  |

The payload of a PRIORITY frame contains the following fields:

  • E: A single bit flag indicates that the stream dependency is exclusive, see Section 5.3.
  • Stream Dependency: A 31-bit stream identifier for the stream that this stream depends on, see Section 5.3.
  • Weight: An 8-bit weight for the identified stream dependency, see Section 5.3. Add one to the value to obtain a weight between 1 and 256.


  • E : 一位的標記,指示流的依賴是專有的,見章節5.3
  • Stream Dependency : 標識流所依賴的流的31位流標識符,見章節5.3
  • Weight: 流的依賴的的權重(8位),見章節5.3。添加一個1-256的權重值。

The PRIORITY frame does not define any flags.


The PRIORITY frame is associated with an existing stream. If a PRIORITY frame is received with a stream identifier of 0x0, the recipient MUST respond with a connection error (Section 5.4.1) of type PROTOCOL_ERROR.


The PRIORITY frame can be sent on a stream in any of the "reserved (remote)", "open", "half closed (local)", "half closed (remote)", or "closed" states, though it cannot be sent between consecutive frames that comprise a single header block (Section 4.3). Note that this frame could arrive after processing or frame sending has completed, which would cause it to have no effect on the current stream. For a stream that is in the "half closed (remote)" or "closed" - state, this frame can only affect processing of the current stream and not frame transmission.


The PRIORITY frame is the only frame that can be sent for a stream in the "closed" state. This allows for the reprioritization of a group of dependent streams by altering the priority of a parent stream, which might be closed. However, a PRIORITY frame sent on a closed stream risks being ignored due to the peer having discarded priority state information for that stream.



The RST_STREAM frame (type=0x3) allows for abnormal termination of a stream. When sent by the initiator of a stream, it indicates that they wish to cancel the stream or that an error condition has occurred. When sent by the receiver of a stream, it indicates that either the receiver is rejecting the stream, requesting that the stream be cancelled, or that an error condition has occurred.


 0                   1                   2                   3
 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
 |                        Error Code (32)                        |

The RST_STREAM frame contains a single unsigned, 32-bit integer identifying the error code (Section 7). The error code indicates why the stream is being terminated.

RST_STREAM 幀由一個無符號的32位整數標記錯誤碼。錯誤碼指明流被終止的原因。

The RST_STREAM frame does not define any flags.

RST_STREAM 幀未定義任何標記。

The RST_STREAM frame fully terminates the referenced stream and causes it to enter the closed state. After receiving a RST_STREAM on a stream, the receiver MUST NOT send additional frames for that stream. However, after sending the RST_STREAM, the sending endpoint MUST be prepared to receive and process additional frames sent on the stream that might have been sent by the peer prior to the arrival of the RST_STREAM.

RST_STREAM 幀完全終止相關的流並使其轉入關閉狀態。在接收到流的RST_STREAM幀後,接收端絕對不能在流上發送額外的幀。然而,在發送RST_STREAM幀後,發送端必須要準備接收並處理流上的其他幀,因為對等端有可能在收到RST_STREAM幀前就已經發送這些幀。

RST_STREAM frames MUST be associated with a stream. If a RST_STREAM frame is received with a stream identifier of 0x0, the recipient MUST treat this as a connection error (Section 5.4.1) of type PROTOCOL_ERROR.

RST_STREAM 幀必須與流相關聯。如果接收端收到流標示符為0x0的RST_STREAM 幀,必須作為類型為協議錯誤的連接錯誤(章節5.4.1)處理。

RST_STREAM frames MUST NOT be sent for a stream in the "idle" state. If a RST_STREAM frame identifying an idle stream is received, the recipient MUST treat this as a connection error (Section 5.4.1) of type PROTOCOL_ERROR.


6.5 SETTINGS 設置幀

The SETTINGS frame (type=0x4) conveys configuration parameters that affect how endpoints communicate, such as preferences and constraints on peer behavior. The SETTINGS frame is also used to acknowledge the receipt of those parameters. Individually, a SETTINGS parameter can also be referred to as a "setting".


SETTINGS parameters are not negotiated; they describe characteristics of the sending peer, which are used by the receiving peer. Different values for the same parameter can be advertised by each peer. For example, a client might set a high initial flow control window, whereas a server might set a lower value to conserve resources.


A SETTINGS frame MUST be sent by both endpoints at the start of a connection, and MAY be sent at any other time by either endpoint over the lifetime of the connection. Implementations MUST support all of the parameters defined by this specification.


Each parameter in a SETTINGS frame replaces any existing value for that parameter. Parameters are processed in the order in which they appear, and a receiver of a SETTINGS frame does not need to maintain any state other than the current value of its parameters. Therefore, the value of a SETTINGS parameter is the last value that is seen by a receiver.


SETTINGS parameters are acknowledged by the receiving peer. To enable this, the SETTINGS frame defines the following flag:


ACK (0x1) : Bit 1 being set indicates that this frame acknowledges receipt and application of the peer's SETTINGS frame. When this bit is set, the payload of the SETTINGS frame MUST be empty. Receipt of a SETTINGS frame with the ACK flag set and a length field value other than 0 MUST be treated as a connection error (Section 5.4.1) of type FRAME_SIZE_ERROR. For more info, see Settings Synchronization (Section 6.5.3).

ACK (0x1) : 位1表示設置幀已被接收端接收並應用。如果這個位設置了,設置幀的載體必須為空。接收到字段長度不是0的帶有ACK標記的設置幀必須作為類型為幀大小錯誤的連接錯誤(章節5.4.1)處理,更多信息,見同步設置(章節6.5.3)。

SETTINGS frames always apply to a connection, never a single stream. The stream identifier for a SETTINGS frame MUST be zero (0x0). If an endpoint receives a SETTINGS frame whose stream identifier field is anything other than 0x0, the endpoint MUST respond with a connection error (Section 5.4.1) of type PROTOCOL_ERROR.


The SETTINGS frame affects connection state. A badly formed or incomplete SETTINGS frame MUST be treated as a connection error (Section 5.4.1) of type PROTOCOL_ERROR.


6.5.1 SettingFormat 設置幀格式

The payload of a SETTINGS frame consists of zero or more parameters, each consisting of an unsigned 16-bit setting identifier and an unsigned 32-bit value.


 0                   1                   2                   3
 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
 |Identifier (8) |                 Value (32)                  ...
 ...Value        |

6.5.2 Defined SETTINGS Parameters 設置幀參數

The following parameters are defined:

  • SETTINGS_HEADER_TABLE_SIZE (0x1):Allows the sender to inform the remote endpoint of the maximum size of the header compression table used to decode header blocks. The encoder can select any size equal to or less than this value by using signaling specific to the header compression format inside a header block. The initial value is 4,096 bytes.
  • SETTINGS_ENABLE_PUSH (0x2):This setting can be use to disable server push (Section 8.2). An endpoint MUST NOT send a PUSH_PROMISE frame if it receives this parameter set to a value of 0. An endpoint that has both set this parameter to 0 and had it acknowledged MUST treat the receipt of a PUSH_PROMISE frame as a connection error (Section 5.4.1) of type PROTOCOL_ERROR. The initial value is 1, which indicates that server push is permitted. Any value other than 0 or 1 MUST be treated as a connection error (Section 5.4.1) of type PROTOCOL_ERROR.
  • SETTINGS_MAX_CONCURRENT_STREAMS (0x3):Indicates the maximum number of concurrent streams that the sender will allow. This limit is directional: it applies to the number of streams that the sender permits the receiver to create. Initially there is no limit to this value. It is recommended that this value be no smaller than 100, so as to not unnecessarily limit parallelism. A value of 0 for SETTINGS_MAX_CONCURRENT_STREAMS SHOULD NOT be treated as special by endpoints. A zero value does prevent the creation of new streams, however this can also happen for any limit that is exhausted with active streams. Servers SHOULD only set a zero value for short durations; if a server does not wish to accept requests, closing the connection could be preferable.
  • SETTINGS_INITIAL_WINDOW_SIZE (0x4):Indicates the sender's initial window size (in bytes) for stream level flow control. The initial value is 65,535. This setting affects the window size of all streams, including existing streams, see Section 6.9.2. Values above the maximum flow control window size of 231 - 1 MUST be treated as a connection error (Section 5.4.1) of type FLOW_CONTROL_ERROR.


  • SETTINGS_HEADER_TABLE_SIZE (1) : 允許發送端通知遠端終端解碼報頭區塊的報頭壓縮表的最大承載量。這個編碼器可以選擇在報頭區塊中使用特定信號來減少報頭壓縮的大小(???)。初始值是4,096個字節。
  • SETTINGS_ENABLE_PUSH (2) : 這個參數可以用來關閉服務器推送。終端在接收到此參數為0的情況下絕對不能發送服務器推送承諾幀。終端在已經設置此參數為0並且承認的情況下必須對接收到的服務器推送作為類型為協議錯誤的連接錯誤處理。 初始值是1,表示推送是許可的。任何不是0或1的值必須作為類型為協議錯誤的連接錯誤處理。
  • SETTINGS_MAX_CONCURRENT_STREAMS (3) : 標明發送者允許的最大並發流。此限制是定向的:它適用於發送端允許接收端創建的最大並發流的數量。初始化時這個值沒有限制。建議值不要大於100,以免不必要的限制並行。 此設置為0的值不應該被終端認為是特殊的。0的值阻止了新的流的創建,另外它也適用於被激活的流用盡的任何限制。對於短連接不應該設置此參數為0;如果服務端不希望接收任何請求,最佳的做法是關閉連接。
  • SETTINGS_INITIAL_WINDOW_SIZE (4) : 表示發送端對流層流量控制的初始窗口大小(字節單位)。初始值是65,535。 這個參數影響了所有流的窗口大小,包括現有的流。見章節6.9.2. 流量控制窗口大小值大於2的31次方-1的必須被作為流量控制錯誤的連接錯誤處理。

An endpoint that receives a SETTINGS frame with any unknown or unsupported identifier MUST ignore that setting.


6.5.3 Settings Synchronization 設置同步

Most values in SETTINGS benefit from or require an understanding of when the peer has received and applied the changed the communicated parameter values. In order to provide such synchronization timepoints, the recipient of a SETTINGS frame in which the ACK flag is not set MUST apply the updated parameters as soon as possible upon receipt.


The values in the SETTINGS frame MUST be applied in the order they appear, with no other frame processing between values. Once all values have been applied, the recipient MUST immediately emit a SETTINGS frame with the ACK flag set. Upon receiving a SETTINGS frame with the ACK flag set, the sender of the altered parameters can rely upon their application.


If the sender of a SETTINGS frame does not receive an acknowledgement within a reasonable amount of time, it MAY issue a connection error (Section 5.4.1) of type SETTINGS_TIMEOUT.


6.6 PUSH_PROMISE 推送承諾幀

The PUSH_PROMISE frame (type=0x5) is used to notify the peer endpoint in advance of streams the sender intends to initiate. The PUSH_PROMISE frame includes the unsigned 31-bit identifier of the stream the endpoint plans to create along with a set of headers that provide additional context for the stream. Section 8.2 contains a thorough description of the use of PUSH_PROMISE frames.


 0                   1                   2                   3
 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
 | [Pad High(8)] | [Pad Low (8)] |X|  Promised Stream ID (31)  ...
 ...    Promised Stream ID       | Header Block Fragment (*)   ...
 |                   Header Block Fragment (*)                 ...
 |                           Padding (*)                       ...

The PUSH_PROMISE frame payload has the following fields:

  • Pad Length:An 8-bit field containing the length of the frame padding in units of octets. This field is optional and is only present if the PADDED flag is set.
  • R:A single reserved bit.
  • Promised Stream ID:This unsigned 31-bit integer identifies the stream the endpoint intends to start sending frames for. The promised stream identifier MUST be a valid choice for the next stream sent by the sender (see new stream identifier (Section 5.1.1)).
  • Header Block Fragment: header block fragment (Section 4.3) containing request header fields.
  • Padding:Padding octets.


  • Pad High : 填充大小高位。這個字段只有在PAD_HIGH標記設置的情況下才呈現。
  • Pad Low : 填充大小低位。這個字段只有在PAD_LOW標記設置的情況下才呈現。
  • X : 單獨的保留位。
  • Promised Stream ID : 這個無符號31位整數表示終端準備發送的流標記。被承諾的流標記必須對發送端準備發送的下一個流來說是有效選擇。
  • Header Block Fragment : 包含請求頭字段的報頭區塊碎片(章節5.1.1)。
  • Padding : 填充字節。

The PUSH_PROMISE frame defines the following flags:

  • END_HEADERS (0x4): Bit 3 being set indicates that this frame contains an entire header block (Section 4.3) and is not followed by any CONTINUATION frames. A PUSH_PROMISE frame without the END_HEADERS flag set MUST be followed by a CONTINUATION frame for the same stream. A receiver MUST treat the receipt of any other type of frame or a frame on a different stream as a connection error (Section 5.4.1) of type PROTOCOL_ERROR.
  • PADDED (0x8): Bit 4 being set indicates that the Pad Length field is present.


  • END_HEADERS (0x4) : 位3 表明幀包含了整個報頭區塊(章節4.3)並且不跟著延續幀。 不帶有END_HEADERS標記的推送承諾幀在同個流上面後面必須跟著延續幀。接收端接收到任何其他類型或者其他流觴的幀必須作為類型為協議錯誤的連接錯誤(章節5.4.1)處理。
  • PADDED (0x8) : 位4 表明Pad長度字段是已設置。

PUSH_PROMISE frames MUST be associated with an existing, peer-initiated stream. The stream identifier of a PUSH_PROMISE frame indicates the stream it is associated with. If the stream identifier field specifies the value 0x0, a recipient MUST respond with a connection error (Section 5.4.1) of type PROTOCOL_ERROR.


Promised streams are not required to be used in the order they are promised. The PUSH_PROMISE only reserves stream identifiers for later use.


PUSH_PROMISE MUST NOT be sent if the SETTINGS_ENABLE_PUSH setting of the peer endpoint is set to 0. An endpoint that has set this setting and has received acknowledgement MUST treat the receipt of a PUSH_PROMISE frame as a connection error (Section 5.4.1) of type PROTOCOL_ERROR.


Recipients of PUSH_PROMISE frames can choose to reject promised streams by returning a RST_STREAM referencing the promised stream identifier back to the sender of the PUSH_PROMISE.


A PUSH_PROMISE frame modifies the connection state in two ways. The inclusion of a header block (Section 4.3) potentially modifies the state maintained for header compression. PUSH_PROMISE also reserves a stream for later use, causing the promised stream to enter the "reserved" state. A sender MUST NOT send a PUSH_PROMISE on a stream unless that stream is either "open" or "half closed (remote)"; the sender MUST ensure that the promised stream is a valid choice for a new stream identifier (Section 5.1.1) (that is, the promised stream MUST be in the "idle" state).


Since PUSH_PROMISE reserves a stream, ignoring a PUSH_PROMISE frame causes the stream state to become indeterminate. A receiver MUST treat the receipt of a PUSH_PROMISE on a stream that is neither "open" nor "half closed (local)" as a connection error (Section 5.4.1) of type PROTOCOL_ERROR. Similarly, a receiver MUST treat the receipt of a PUSH_PROMISE that promises an illegal stream identifier (Section 5.1.1) (that is, an identifier for a stream that is not currently in the "idle" state) as a connection error (Section 5.4.1) of type PROTOCOL_ERROR.

由於PUSH_PROMISE保留了一個流、忽略一個PUSH_PROMISE 幀都會導致流狀態變得不確定。接收端接收到流狀態不是“打開”或者“半封閉(本地)”的流的推送承諾幀必須作為類型為協議錯誤的連接錯誤(章節5.4.1)處理。相似的,接收端必須對在一個非法標示(章節5.1.1)的流(即流的標識當前不在空閒狀態)上建立的推送承諾作為類型為協議錯誤的連接錯誤(章節5.4.1)處理。

The PUSH_PROMISE frame includes optional padding. Padding fields and flags are identical to those defined for DATA frames (Section 6.1).



The PING frame (type=0x6) is a mechanism for measuring a minimal round trip time from the sender, as well as determining whether an idle connection is still functional. PING frames can be sent from any endpoint.


 0                   1                   2                   3
 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
 |                                                               |
 |                      Opaque Data (64)                         |
 |                                                               |

In addition to the frame header, PING frames MUST contain 8 octets of data in the payload. A sender can include any value it chooses and use those bytes in any fashion.


Receivers of a PING frame that does not include an ACK flag MUST send a PING frame with the ACK flag set in response, with an identical payload. PING responses SHOULD be given higher priority than any other frame.


The PING frame defines the following flags:

  • ACK (0x1):Bit 1 being set indicates that this PING frame is a PING response. An endpoint MUST set this flag in PING responses. An endpoint MUST NOT respond to PING frames containing this flag.

    PING frames are not associated with any individual stream. If a PING frame is received with a stream identifier field value other than 0x0, the recipient MUST respond with a connection error (Section 5.4.1) of type PROTOCOL_ERROR.


ACK (0x1) : 位1表示PING幀是一個PING響應。終端必須在PING響應中設置此標記。終端絕對不能對包含此標記的PING幀做出響應。


Receipt of a PING frame with a length field value other than 8 MUST be treated as a connection error (Section 5.4.1) of type FRAME_SIZE_ERROR.


6.8 GOAWAY 超時幀

The GOAWAY frame (type=0x7) informs the remote peer to stop creating streams on this connection. GOAWAY can be sent by either the client or the server. Once sent, the sender will ignore frames sent on any new streams with identifiers higher than the included last stream identifier. Receivers of a GOAWAY frame MUST NOT open additional streams on the connection, although a new connection can be established for new streams.


The purpose of this frame is to allow an endpoint to gracefully stop accepting new streams, while still finishing processing of previously established streams. This enables administrative actions, like server maintainence.


There is an inherent race condition between an endpoint starting new streams and the remote sending a GOAWAY frame. To deal with this case, the GOAWAY contains the stream identifier of the last stream which was or might be processed on the sending endpoint in this connection. If the receiver of the GOAWAY has sent data on streams with a higher stream identifier than what is indicated in the GOAWAY frame, those streams are not or will not be processed. The receiver of the GOAWAY frame can treat the streams as though they had never been created at all, thereby allowing those streams to be retried later on a new connection.


Endpoints SHOULD always send a GOAWAY frame before closing a connection so that the remote can know whether a stream has been partially processed or not. For example, if an HTTP client sends a POST at the same time that a server closes a connection, the client cannot know if the server started to process that POST request if the server does not send a GOAWAY frame to indicate what streams it might have acted on.


An endpoint might choose to close a connection without sending GOAWAY for misbehaving peers.


 0                   1                   2                   3
 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
 |X|                  Last-Stream-ID (31)                        |
 |                      Error Code (32)                          |
 |                  Additional Debug Data (*)                    |

The GOAWAY frame does not define any flags.


The GOAWAY frame applies to the connection, not a specific stream. An endpoint MUST treat a GOAWAY frame with a stream identifier other than 0x0 as a connection error (Section 5.4.1) of type PROTOCOL_ERROR.


The last stream identifier in the GOAWAY frame contains the highest numbered stream identifier for which the sender of the GOAWAY frame might have taken some action on, or might yet take action on. All streams up to and including the identified stream might have been processed in some way. The last stream identifier can be set to 0 if no streams were processed.


Note:In this context, "processed" means that some data from the stream was passed to some higher layer of software that might have taken some action as a result.


If a connection terminates without a GOAWAY frame, the last stream identifier is effectively the highest possible stream identifier.


On streams with lower or equal numbered identifiers that were not closed completely prior to the connection being closed, re-attempting requests, transactions, or any protocol activity is not possible, with the exception of idempotent actions like HTTP GET, PUT, or DELETE. Any protocol activity that uses higher numbered streams can be safely retried using a new connection.

連接關閉前小於或等於標識符上的流沒有完全關閉的,重試請求,交換,或者任何協議活動都是不可能的(例如HTTP GET,PUT,或者刪除等等冪行為例外)。任何使用更高的流數值的協議行為可以在新的連接上安全地重試。

Activity on streams numbered lower or equal to the last stream identifier might still complete successfully. The sender of a GOAWAY frame might gracefully shut down a connection by sending a GOAWAY frame, maintaining the connection in an open state until all in-progress streams complete.


An endpoint MAY send multiple GOAWAY frames if circumstances change. For instance, an endpoint that sends GOAWAY with NO_ERROR during graceful shutdown could subsequently encounter an condition that requires immediate termination of the connection. The last stream identifier from the last GOAWAY frame received indicates which streams could have been acted upon. Endpoints MUST NOT increase the value they send in the last stream identifier, since the peers might already have retried unprocessed requests on another connection.


A client that is unable to retry requests loses all requests that are in flight when the server closes the connection. This is especially true for intermediaries that might not be serving clients using HTTP/2. A server that is attempting to gracefully shut down a connection SHOULD send an initial GOAWAY frame with the last stream identifier set to 231-1 and a NO_ERROR code. This signals to the client that a shutdown is imminent and that no further requests can be initiated. After waiting at least one round trip time, the server can send another GOAWAY frame with an updated last stream identifier. This ensures that a connection can be cleanly shut down without losing requests.

服務端關閉連接時,終端無法重試請求的將丟失所有正在發送的請求。尤其是針對中介端無法使用HTTP/2服務客戶端的時候。無負擔嘗試優雅關閉連接時應當發送一個攜帶2^{31} -1 大小的流標識符和一個錯誤碼的初始超時幀。這個信號對客戶端來說意味著即將關閉連接並且不能建立更多請求了。在等待至少一個RTT時間之後,服務端能發送另外一個帶有更新後的最終流標識符超時幀。這個確保了連接能徹底的關閉而不用丟失請求。

After sending a GOAWAY frame, the sender can discard frames for streams with identifiers higher than the identified last stream. However, any frames that alter connection state cannot be completely ignored. For instance, HEADERS, PUSH_PROMISE and CONTINUATION frames MUST be minimally processed to ensure the state maintained for header compression is consistent (see Section 4.3); similarly DATA frames MUST be counted toward the connection flow control window. Failure to process these frames can cause flow control or header compression state to become unsynchronized.


The GOAWAY frame also contains a 32-bit error code (Section 7) that contains the reason for closing the connection.


Endpoints MAY append opaque data to the payload of any GOAWAY frame. Additional debug data is intended for diagnostic purposes only and carries no semantic value. Debug information could contain security- or privacy-sensitive data. Logged or otherwise persistently stored debug data MUST have adequate safeguards to prevent unauthorized access.



The WINDOW_UPDATE frame (type=0x8) is used to implement flow control; see Section 5.2 for an overview.


Flow control operates at two levels: on each individual stream and on the entire connection.


Both types of flow control are hop-by-hop; that is, only between the two endpoints. Intermediaries do not forward WINDOW_UPDATE frames between dependent connections. However, throttling of data transfer by any receiver can indirectly cause the propagation of flow control information toward the original sender.


Flow control only applies to frames that are identified as being subject to flow control. Of the frame types defined in this document, this includes only DATA frames. Frames that are exempt from flow control MUST be accepted and processed, unless the receiver is unable to assign resources to handling the frame. A receiver MAY respond with a stream error (Section 5.4.2) or connection error (Section 5.4.1) of type FLOW_CONTROL_ERROR if it is unable to accept a frame.


 0                   1                   2                   3
 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
 |X|              Window Size Increment (31)                     |

The payload of a WINDOW_UPDATE frame is one reserved bit, plus an unsigned 31-bit integer indicating the number of bytes that the sender can transmit in addition to the existing flow control window. The legal range for the increment to the flow control window is 1 to 231 - 1 (0x7fffffff) bytes.

WINDOW_UPDATE幀的載體是一個保留字節,加上一個無符號31為整數表明發送端除了現有的流量控制窗口可以發送的字節數。留空控制窗口有效的增量範圍是$1 至 2^{31}-1$(0x7fffffff) 字節。

The WINDOW_UPDATE frame does not define any flags.


The WINDOW_UPDATE frame can be specific to a stream or to the entire connection. In the former case, the frame's stream identifier indicates the affected stream; in the latter, the value "0" indicates that the entire connection is the subject of the frame.


WINDOW_UPDATE can be sent by a peer that has sent a frame bearing the END_STREAM flag. This means that a receiver could receive a WINDOW_UPDATE frame on a "half closed (remote)" or "closed" stream. A receiver MUST NOT treat this as an error, see Section 5.1.


A receiver that receives a flow controlled frame MUST always account for its contribution against the connection flow control window, unless the receiver treats this as a connection error (Section 5.4.1). This is necessary even if the frame is in error. Since the sender counts the frame toward the flow control window, if the receiver does not, the flow control window at sender and receiver can become different.


6.9.1 The Flow Control Window 流量控制窗口

Flow control in HTTP/2 is implemented using a window kept by each sender on every stream. The flow control window is a simple integer value that indicates how many bytes of data the sender is permitted to transmit; as such, its size is a measure of the buffering capacity of the receiver.


Two flow control windows are applicable: the stream flow control window and the connection flow control window. The sender MUST NOT send a flow controlled frame with a length that exceeds the space available in either of the flow control windows advertised by the receiver. Frames with zero length with the END_STREAM flag set (that is, an empty DATA frame) MAY be sent if there is no available space in either flow control window.


For flow control calculations, the 8 byte frame header is not counted.


After sending a flow controlled frame, the sender reduces the space available in both windows by the length of the transmitted frame.


The receiver of a frame sends a WINDOW_UPDATE frame as it consumes data and frees up space in flow control windows. Separate WINDOW_UPDATE frames are sent for the stream and connection level flow control windows.


A sender that receives a WINDOW_UPDATE frame updates the corresponding window by the amount specified in the frame.


A sender MUST NOT allow a flow control window to exceed 231 - 1 bytes. If a sender receives a WINDOW_UPDATE that causes a flow control window to exceed this maximum it MUST terminate either the stream or the connection, as appropriate. For streams, the sender sends a RST_STREAM with the error code of FLOW_CONTROL_ERROR code; for the connection, a GOAWAY frame with a FLOW_CONTROL_ERROR code.


Flow controlled frames from the sender and WINDOW_UPDATE frames from the receiver are completely asynchronous with respect to each other. This property allows a receiver to aggressively update the window size kept by the sender to prevent streams from stalling.


6.9.2 Initial Flow Control Window Size 流量控制窗口初始值

When an HTTP/2 connection is first established, new streams are created with an initial flow control window size of 65,535 bytes. The connection flow control window is 65,535 bytes. Both endpoints can adjust the initial window size for new streams by including a value for SETTINGS_INITIAL_WINDOW_SIZE in the SETTINGS frame that forms part of the connection preface. The connection flow control window can only be changed using WINDOW_UPDATE frames.


Prior to receiving a SETTINGS frame that sets a value for SETTINGS_INITIAL_WINDOW_SIZE, an endpoint can only use the default initial window size when sending flow controlled frames. Similarly, the connection flow control window is set to the default initial window size until a WINDOW_UPDATE frame is received.


A SETTINGS frame can alter the initial flow control window size for all current streams. When the value of SETTINGS_INITIAL_WINDOW_SIZE changes, a receiver MUST adjust the size of all stream flow control windows that it maintains by the difference between the new value and the old value.


A change to SETTINGS_INITIAL_WINDOW_SIZE can cause the available space in a flow control window to become negative. A sender MUST track the negative flow control window, and MUST NOT send new flow controlled frames until it receives WINDOW_UPDATE frames that cause the flow control window to become positive.


For example, if the client sends 60KB immediately on connection establishment, and the server sets the initial window size to be 16KB, the client will recalculate the available flow control window to be -44KB on receipt of the SETTINGS frame. The client retains a negative flow control window until WINDOW_UPDATE frames restore the window to being positive, after which the client can resume sending.


A SETTINGS frame cannot alter the connection flow control window.


An endpoint MUST treat a change to SETTINGS_INITIAL_WINDOW_SIZE that causes any flow control window to exceed the maximum size as a connection error (Section 5.4.1) of type FLOW_CONTROL_ERROR.

終端必須將SETTINGS_INITIAL_WINDOW_SIZE的修改導致流量控制窗口超過最大值的情況作為類型為流量控制錯誤的連接錯誤(章節 5.4.1)處理。

6.9.3 Reducing the Stream Window Size 減少流量窗口大小

A receiver that wishes to use a smaller flow control window than the current size can send a new SETTINGS frame. However, the receiver MUST be prepared to receive data that exceeds this window size, since the sender might send data that exceeds the lower limit prior to processing the SETTINGS frame.


After sending a SETTINGS frame that reduces the initial flow control window size, a receiver has two options for handling streams that exceed flow control limits:


  1. The receiver can immediately send RST_STREAM with FLOW_CONTROL_ERROR error code for the affected streams.
  2. The receiver can accept the streams and tolerate the resulting head of line blocking, sending WINDOW_UPDATE frames as it consumes data.

  3. 接收端可以針對受影響的流立即發送帶有流量控制錯誤錯誤碼的RST_STREAM幀。

  4. 接收端如果在消耗數據可以接受流並且忍受報頭阻塞的結果,並發送WINDOW_UPDATE幀。


The CONTINUATION frame (type=0x9) is used to continue a sequence of header block fragments (Section 4.3). Any number of CONTINUATION frames can be sent on an existing stream, as long as the preceding frame is on the same stream and is a HEADERS, PUSH_PROMISE or CONTINUATION frame without the END_HEADERS flag set.


  0                   1                   2                   3
  0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
 |                   Header Block Fragment (*)                 ...

The CONTINUATION frame payload contains a header block fragment (Section 4.3).


The CONTINUATION frame defines the following flag:

  • END_HEADERS (0x4):Bit 3 being set indicates that this frame ends a header block (Section 4.3). If the END_HEADERS bit is not set, this frame MUST be followed by another CONTINUATION frame. A receiver MUST treat the receipt of any other type of frame or a frame on a different stream as a connection error (Section 5.4.1) of type PROTOCOL_ERROR.


  • END_HEADERS (0x4) : 位3設置指示這個幀的報頭區塊的終止(章節4.3)。 如果END_HEADERS位沒有被設置,這個幀必須跟著另一個延續幀。接收到必須將收到其他類型的幀或者其他流上的幀錯位類型為協議錯誤的連接錯誤(章節5.4.1)處理。

The CONTINUATION frame changes the connection state as defined in Section 4.3.


CONTINUATION frames MUST be associated with a stream. If a CONTINUATION frame is received whose stream identifier field is 0x0, the recipient MUST respond with a connection error (Section 5.4.1) of type PROTOCOL_ERROR.


A CONTINUATION frame MUST be preceded by a HEADERS, PUSH_PROMISE or CONTINUATION frame without the END_HEADERS flag set. A recipient that observes violation of this rule MUST respond with a connection error (Section 5.4.1) of type PROTOCOL_ERROR.


7 Error Codes 錯誤碼

Error codes are 32-bit fields that are used in RST_STREAM and GOAWAY frames to convey the reasons for the stream or connection error.


Error codes share a common code space. Some error codes apply only to either streams or the entire connection and have no defined semantics in the other context.


The following error codes are defined:

  • NO_ERROR (0x0):The associated condition is not as a result of an error. For example, a GOAWAY might include this code to indicate graceful shutdown of a connection.
  • PROTOCOL_ERROR (0x1):The endpoint detected an unspecific protocol error. This error is for use when a more specific error code is not available.
  • INTERNAL_ERROR (0x2):The endpoint encountered an unexpected internal error.
  • FLOW_CONTROL_ERROR (0x3):The endpoint detected that its peer violated the flow control protocol.
  • SETTINGS_TIMEOUT (0x4):The endpoint sent a SETTINGS frame, but did not receive a response in a timely manner. See Settings Synchronization (Section 6.5.3).
  • STREAM_CLOSED (0x5):The endpoint received a frame after a stream was half closed.
  • FRAME_SIZE_ERROR (0x6):The endpoint received a frame that was larger than the maximum size that it supports.
  • REFUSED_STREAM (0x7):The endpoint refuses the stream prior to performing any application processing, see Section 8.1.4 for details.
  • CANCEL (0x8):Used by the endpoint to indicate that the stream is no longer needed.
  • COMPRESSION_ERROR (0x9):The endpoint is unable to maintain the header compression context for the connection.
  • CONNECT_ERROR (0xa):The connection established in response to a CONNECT request (Section 8.3) was reset or abnormally closed.
  • ENHANCE_YOUR_CALM (0xb):The endpoint detected that its peer is exhibiting a behavior that might be generating excessive load.
  • INADEQUATE_SECURITY (0xc):The underlying transport has properties that do not meet minimum security requirements (see Section 9.2).


  • NO_ERROR (0) : 相關的條件並不是錯誤的結果。例如超時幀可以攜帶此錯誤碼指示連接的平滑關閉。
  • PROTOCOL_ERROR (1) : 終端檢測到一個不確定的協議錯誤。這個錯誤用在一個更具體的錯誤碼不可用的時候。
  • INTERNAL_ERROR (2) : 終端遇到意外的內部錯誤。
  • FLOW_CONTROL_ERROR (3) : 終端檢測到對等端違反了流量控制協議。
  • SETTINGS_TIMEOUT (4) : 終端發送了設置幀,但是沒有及時收到響應。見Settings Synchronization。
  • STREAM_CLOSED (5) : 終端在流半封閉的時候收到幀。
  • FRAME_SIZE_ERROR (6) : 終端收到大小超過最大尺寸的幀。
  • REFUSED_STREAM (7) : 終端拒絕流在它執行任何應用處理之前,詳見Reliability(章節 8.1.4)
  • CANCEL (8) : 終端使用這個標示某個流不再需要。
  • COMPRESSION_ERROR (9) : 終端無法維持報頭壓縮上下文的連接
  • CONNECT_ERROR (10) : 響應某個連接請求建立的連接被服為異常關閉。
  • ENHANCE_YOUR_CALM (11) : 終端檢測出對等端在表現出可能會產生過大負荷的行為。
  • INADEQUATE_SECURITY (12) : 基礎傳輸包含屬性不滿足文檔或者終端申明的最小要求。

Unknown or unsupported error codes MUST NOT trigger any special behavior. These MAY be treated by an implementation as being equivalent to INTERNAL_ERROR.


8 HTTP Message Exchanges HTTP消息交換

HTTP/2 is intended to be as compatible as possible with current uses of HTTP. This means that, from the application perspective, the features of the protocol are largely unchanged. To achieve this, all request and response semantics are preserved, although the syntax of conveying those semantics has changed.


Thus, the specification and requirements of HTTP/1.1 Semantics and Content [RFC7231], Conditional Requests [RFC7232], Range Requests [RFC7233], Caching [RFC7234] and Authentication [RFC7235] are applicable to HTTP/2. Selected portions of HTTP/1.1 Message Syntax and Routing [RFC7230], such as the HTTP and HTTPS URI schemes, are also applicable in HTTP/2, but the expression of those semantics for this protocol are defined in the sections below.

因此,HTTP/1.1語義與內容、有條件的請求、範圍請求、緩存與驗證定義的規範與要求同樣適用於HTTP/2。HTTP/1.1消息語法與路由選定的內容,例如HTTP與HTTPS URI方案,也同樣適用於HTTP/2,但是表達這些協議的語義在下面的章節定義。

8.1 HTTP Request/Response Exchange HTTP 請求/響應交換

A client sends an HTTP request on a new stream, using a previously unused stream identifier (Section 5.1.1). A server sends an HTTP response on the same stream as the request.


An HTTP message (request or response) consists of:

  1. one HEADERS frame (followed by zero or more CONTINUATION frames) containing the message headers (see [RFC7230], Section 3.2), and
  2. zero or more DATA frames containing the message payload (see [RFC7230], Section 3.3), and
  3. optionally, one HEADERS frame, followed by zero or more CONTINUATION frames containing the trailer-part, if present (see [RFC7230], Section 4.1.2).


  1. 一個報頭幀,後面跟著0個或多個延續幀(包含消息報頭;見RFC7230),以及
  2. 0個或多個數據幀(包含消息載荷,見RFC7230章節3.3),以及
  3. 一個可選的版頭,後面跟著0個或多個延續幀(如果存在,包含尾部部分,見RFC7230章節4.1.2)

The last frame in the sequence bears an END_STREAM flag, noting that a HEADERS frame bearing the END_STREAM flag can be followed by CONTINUATION frames that carry any remaining portions of the header block.


Other frames (from any stream) MUST NOT occur between either HEADERS frame and any CONTINUATION frames that might follow.


Otherwise, frames MAY be interspersed on the stream between these frames, but those frames do not carry HTTP semantics. In particular, HEADERS frames (and any CONTINUATION frames that follow) other than the first and optional last frames in this sequence do not carry HTTP semantics.


Trailing header fields are carried in a header block that also terminates the stream. That is, a sequence starting with a HEADERS frame, followed by zero or more CONTINUATION frames, where the HEADERS frame bears an END_STREAM flag. Header blocks after the first that do not terminate the stream are not part of an HTTP request or response.


An HTTP request/response exchange fully consumes a single stream. A request starts with the HEADERS frame that puts the stream into an "open" state. The request ends with a frame bearing END_STREAM, which causes the stream to become "half closed (local)" for the client and "half closed (remote)" for the server. A response starts with a HEADERS frame and ends with a frame bearing END_STREAM, which places the stream in the "closed" state.

一個HTTP 請求/響應的數據交換在同一個流上進行。一個請求由是流進入打開狀態的報頭幀開始,並由一個攜帶使流對客戶端進入半封閉的END_STREAM標記的幀結束,另外可選的後面可以跟著延續幀,使流進入關閉狀態。一個響應從HEADERS幀開始並且結束於一個放在封閉狀態中支撐END_STREAM的幀

8.1.1 Informational Responses 響應信息

The 1xx series of HTTP response status codes ([RFC7231], Section 6.2) are not supported in HTTP/2.


The most common use case for 1xx is using an Expect header field with a 100-continue token (colloquially, "Expect/continue") to indicate that the client expects a 100 (Continue) non-final response status code, receipt of which indicates that the client should continue sending the request body if it has not already done so.


Typically, Expect/continue is used by clients wishing to avoid sending a large amount of data in a request body, only to have the request rejected by the origin server, thereby leaving the connection potentially unusable.


HTTP/2 does not enable the Expect/continue mechanism; if the server sends a final status code to reject the request, it can do so without making the underlying connection unusable.


Note that this means HTTP/2 clients sending requests with bodies may waste at least one round trip of sent data when the request is rejected. This can be mitigated by restricting the amount of data sent for the first round trip by bandwidth-constrained clients, in anticipation of a final status code.


Other defined 1xx status codes are not applicable to HTTP/2. For example, the semantics of 101 (Switching Protocols) aren't suitable to a multiplexed protocol. Likewise, 102 (Processing) [RFC2518] is no longer necessary to ensure connection liveness, because HTTP/2 has a separate means of keeping the connection alive. The use of the 102 (Processing) status code for progress reporting has since been deprecated and is not retained.


This difference between protocol versions necessitates special handling by intermediaries that translate between them:

  • An intermediary that translates HTTP/1.1 requests to HTTP/2 MUST generate a 100 (Continue) response if a received request includes and Expect header field with a 100-continue token ([RFC7231], Section 5.1.1), unless it can immediately generate a final status code. It MUST NOT forward the 100-continue expectation in the request header fields.
  • An intermediary that translates HTTP/2 to HTTP/1.1 MAY add an Expect header field with a 100-continue expectation when forwarding a request that has a body; see [RFC7231], Section 5.1.1 for specific requirements.
  • An intermediary that gateways HTTP/2 to HTTP/1.1 MUST discard all other 1xx informational responses.


  • 轉換HTTP/1.1到HTTP/2的中介網關如果收到請求包含帶有100-繼續token(RFC7231,章節5.1.1)的期望報頭字段,必須生成一個100(繼續)響應,除非它能馬上生成一個最終狀態碼。絕對不能轉發請求報頭中的100-繼續期望字段。
  • 轉換HTTP/2到HTTP/1.1的中介網關在轉發一個帶有正文的請求時可以添加一個帶有100-繼續的期望報頭字段。特定要求見RFC7231.
  • 轉換HTTP/2到HTTP/1.1的中介網關必須丟棄所有1xx以外的響應信息。

8.1.2 HTTP Header Fields HTTP報頭字段

HTTP header fields carry information as a series of key-value pairs. For a listing of registered HTTP headers, see the Message Header Field Registry maintained at https://www.iana.org/assignments/message-headers.


While HTTP/1.x used the message start-line (see [RFC7230], Section 3.1) to convey the target URI and method of the request, and the status code for the response, HTTP/2 uses special pseudo-headers beginning with ':' character (ASCII 0x3a) for this purpose.

HTTP/1.x使用消息起始線(見RFC7230,章節3.1)來傳達URI目標和請求的方法、以及響應的狀態碼,HTTP/2使用特殊的':'(ASCII 0x3a)開頭的偽頭字符來實現這個目的。

Just as in HTTP/1.x, header field names are strings of ASCII characters that are compared in a case-insensitive fashion. However, header field names MUST be converted to lowercase prior to their encoding in HTTP/2. A request or response containing uppercase header field names MUST be treated as malformed (Section


This means that an intermediary transforming an HTTP/1.x message to HTTP/2 will need to remove any header fields nominated by the Connection header field, along with the Connection header field itself. Such intermediaries SHOULD also remove other connection-specific header fields, such as Keep-Alive, Proxy-Connection, Transfer-Encoding and Upgrade, even if they are not nominated by Connection.


One exception to this is the TE header field, which MAY be present in an HTTP/2 request, but when it is MUST NOT contain any value other than "trailers".

一個例外是TE報頭字段,這個可能在 HTTP/2 請求中保留,但是它不能包含“trailers”以外的值。

Note: : HTTP/2 purposefully does not support upgrade to another protocol. The handshake methods described in Section 3 are believed sufficient to negotiate the use of alternative protocols.

Note: : HTTP/2不支持升級到其他協議。3章節中描述的握手協議被認為足夠用來作為替代協議使用。 Request Header Fields 請求報頭字段

HTTP/2 defines a number of pseudo header fields starting with a colon ':' character that carry information about the request target:

  • The :method header field includes the HTTP method ([RFC7231], Section 4).
  • The :scheme header field includes the scheme portion of the target URI ([RFC3986], Section 3.1). :scheme is not restricted to http and https schemed URIs. A proxy or gateway can translate requests for non-HTTP schemes, enabling the use of HTTP to interact with non-HTTP services.
  • The :authority header field includes the authority portion of the target URI ([RFC3986], Section 3.2). The authority MUST NOT include the deprecated userinfo subcomponent for http or https schemed URIs. To ensure that the HTTP/1.1 request line can be reproduced accurately, this header field MUST be omitted when translating from an HTTP/1.1 request that has a request target in origin or asterisk form (see [RFC7230], Section 5.3). Clients that generate HTTP/2 requests directly SHOULD instead omit the Host header field. An intermediary that converts an HTTP/2 request to HTTP/1.1 MUST create a Host header field if one is not present in a request by copying the value of the :authority header field.
  • The :path header field includes the path and query parts of the target URI (the path-absolute production from [RFC3986] and optionally a '?' character followed by the query production, see [RFC3986], Section 3.3 and [RFC3986], Section 3.4). This field MUST NOT be empty; URIs that do not contain a path component MUST include a value of '/', unless the request is an OPTIONS request in asterisk form, in which case the :path header field MUST include '*'.


  • :method 報頭字段包含了HTTP方法
  • :scheme字段包含了目標URI方案部分。 :scheme並不是被限制於http和https類的URIS。代理或者網路關口可以轉化非HTTP體系的請求使其可以於非HTTP得請求互動
  • :authority報頭字段包含了目標URI的權限部分。這個權限絕對不能包含http:或者https: URIs的廢棄的用戶信息子成份。 為了保證HTTP/1.1請求行能被精確複製,當原始請求有請求目標或者星號形式(見[ http-p1 ],5.3節)的HTTP/1.1請求進行轉換時這個字段必須被忽略。客戶端直接生成HTTP/2請求的相反應該忽略Host報頭字段。如果其中一個請求沒有Host字段,中介端將HTTP/2請求轉換為HTTP/1.1請求的時候必須複製:authority字段的值來生成Host字段。
  • :path字段包含目標URI的路徑及查詢部分(絕對路徑由[RFC3986]以及可選的‘?’字符後面跟著查詢詞組成見xx)。這個字段絕對不能為空;URI不包含path組件的必須包含一個'/'值,除非請求是一個星號形式的可選請求:這種情況下:path報頭字段必須包含""。是一個星號形式的可選請求:這種情況下:path報頭字段必須包含""。 Response Header Fields 響應報頭字段

A single :status header field is defined that carries the HTTP status code field (see [RFC7231], Section 6). This header field MUST be included in all responses, otherwise the response is malformed (Section

定義了一個單獨的:status 報頭字段攜帶了HTTP狀態碼信息(見RFC7231,章節6)。這個報頭字段必須包含在所有的響應中,否則響應就是不規範的(章節8.1.2.5)。

HTTP/2 does not define a way to carry the version or reason phrase that is included in an HTTP/1.1 status line.

HTTP/2沒有定義一種方式攜帶HTTP/1.1狀態行中的版本或原因短語信息。 Header Field Ordering 報頭字段順序

HTTP Header Compression [COMPRESSION] does not preserve the order of header fields, because the relative order of header fields with different names is not important. However, the same header field can be repeated to form a list (see [RFC7230], Section 3.2.2), where the relative order of header field values is significant. This repetition can occur either as a single header field with a comma-separated list of values, or as several header fields with a single value, or any combination thereof. Therefore, in the latter case, ordering needs to be preserved before compression takes place.


To preserve the order of multiple occurrences of a header field with the same name, its ordered values are concatenated into a single value using a zero-valued octet (0x0) to delimit them.


After decompression, header fields that have values containing zero octets (0x0) MUST be split into multiple header fields before being processed.


For example, the following HTTP/1.x header block:


              Content-Type: text/html
              Cache-Control: max-age=60, private
              Cache-Control: must-revalidate

contains three Cache-Control directives; two directives in the first Cache-Control header field, and the third directive in the second Cache-Control field. Before compression, they would need to be converted to a form similar to this (with 0x0 represented as '\0'):


cache-control: max-age=60, private\0must-revalidate
              content-type: text/html

Note here that the ordering between Content-Type and Cache-Control is not preserved, but the relative ordering of the Cache-Control directives - as well as the fact that the first two were comma-separated, while the last was on a different line - is.


Header fields containing multiple values MUST be concatenated into a single value unless the ordering of that header field is known to be not significant.


The special case of set-cookie - which does not form a comma-separated list, but can have multiple values - does not depend on ordering. The set-cookie header field MAY be encoded as multiple header field values, or as a single concatenated value.

特殊情況是設置cookie——不需要形成一個逗號分隔的列表,但是可以有多個值——不需要依賴順序。設置cookie字段可以被編碼成多行報頭字段值,或者單個的連接值。 Compressing the Cookie Header Field 報頭Cookie字段壓縮

The Cookie header field [COOKIE] can carry a significant amount of redundant data.


The Cookie header field uses a semi-colon (";") to delimit cookie-pairs (or "crumbs"). This header field doesn't follow the list construction rules in HTTP (see [RFC7230], Section 3.2.2), which prevents cookie-pairs from being separated into different name-value pairs. This can significantly reduce compression efficiency as individual cookie-pairs are updated.


To allow for better compression efficiency, the Cookie header field MAY be split into separate header fields, each with one or more cookie-pairs. If there are multiple Cookie header fields after decompression, these MUST be concatenated into a single octet string using the two octet delimiter of 0x3B, 0x20 (the ASCII string "; ").

為了更好的壓縮效率,Cookie字段可以被分隔成多個報頭字段,每個包含一個或者多個cookie對。如果解壓後有多個Cookie報頭字段,他們必須由兩個字節的0x3B, 0x20(ASCII";")連接成單個字段。

The Cookie header field MAY be split using a zero octet (0x0), as defined in Section When decoding, zero octets MUST be replaced with the cookie delimiter ("; ").


Therefore, the following sets of Cookie header fields are semantically equivalent, though the final form might appear in a different order after compression and decompression.


  cookie: a=b; c=d; e=f

  cookie: a=b\0c=d; e=f

  cookie: a=b
  cookie: c=d
  cookie: e=f Malformed Messages 不規範的消息

A malformed request or response is one that uses a valid sequence of HTTP/2 frames, but is otherwise invalid due to the presence of prohibited header fields, the absence of mandatory header fields, or the inclusion of uppercase header field names.


A request or response that includes an entity body can include a content-length header field. A request or response is also malformed if the value of a content-length header field does not equal the sum of the DATA frame payload lengths that form the body.


Intermediaries that process HTTP requests or responses (i.e., any intermediary not acting as a tunnel) MUST NOT forward a malformed request or response.


Implementations that detect malformed requests or responses need to ensure that the stream ends. For malformed requests, a server MAY send an HTTP response prior to closing or resetting the stream. Clients MUST NOT accept a malformed response. Note that these requirements are intended to protect against several types of common attacks against HTTP; they are deliberately strict, because being permissive can expose implementations to these vulnerabilities.


8.1.3 Examples 示例

This section shows HTTP/1.1 requests and responses, with illustrations of equivalent HTTP/2 requests and responses.


An HTTP GET request includes request header fields and no body and is therefore transmitted as a single HEADERS frame, followed by zero or more CONTINUATION frames containing the serialized block of request header fields. The HEADERS frame in the following has both the END_HEADERS and END_STREAM flags set; no CONTINUATION frames are sent:

一個帶有請求報頭字段但沒有正文的HTTP GET請求將被轉換成一個單獨的報頭幀,後面跟著0個或者多個包含序列化的報頭字段區塊的延續幀。序列中最後一個報頭幀將有END_HEADERS和END_STREAM標記。

  GET /resource HTTP/1.1           HEADERS
  Host: example.org          ==>     + END_STREAM
  Accept: image/jpeg                 + END_HEADERS
                                       :method = GET
                                       :scheme = https
                                       :path = /resource
                                       host = example.org
                                       accept = image/jpeg

Similarly, a response that includes only response header fields is transmitted as a HEADERS frame (again, followed by zero or more CONTINUATION frames) containing the serialized block of response header fields.


  HTTP/1.1 304 Not Modified        HEADERS
  ETag: "xyzzy"              ==>     + END_STREAM
  Expires: Thu, 23 Jan ...           + END_HEADERS
                                       :status = 304
                                       etag: "xyzzy"
                                       expires: Thu, 23 Jan ...

An HTTP POST request that includes request header fields and payload data is transmitted as one HEADERS frame, followed by zero or more CONTINUATION frames containing the request header fields, followed by one or more DATA frames, with the last CONTINUATION (or HEADERS) frame having the END_HEADERS flag set and the final DATA frame having the END_STREAM flag set:

帶有報頭和載荷數據的POST HTTP請求將被轉換成一個報頭幀,後面跟著0個或者多個帶有請求報頭字段的延續幀,同時後面跟著一個或者多個數據幀。延續幀或者報頭幀的最後一幀有END_HEADERS標記,最後一個數據幀擁有END_STREAM標記。

 POST /resource HTTP/1.1          HEADERS
  Host: example.org          ==>     - END_STREAM
  Content-Type: image/jpeg           + END_HEADERS
  Content-Length: 123                  :method = POST
                                       :scheme = https
  {binary data}                        :path = /resource
                                       :authority = example.org
                                       content-type = image/jpeg
                                       content-length = 123

                                     + END_STREAM
                                   {binary data}

Note that data contributing to any given header field could be spread between header block fragments. The allocation of header fields to frames in this example is illustrative only.


A response that includes header fields and payload data is transmitted as a HEADERS frame, followed by zero or more CONTINUATION frames, followed by one or more DATA frames, with the last DATA frame in the sequence having the END_STREAM flag set:


  HTTP/1.1 200 OK                  HEADERS
  Content-Type: image/jpeg   ==>     - END_STREAM
  Content-Length: 123                + END_HEADERS
                                       :status = 200
  {binary data}                        content-type = image/jpeg
                                       content-length = 123

                                     + END_STREAM
                                   {binary data}

Trailing header fields are sent as a header block after both the request or response header block and all the DATA frames have been sent. The HEADERS frame starting the trailers header block has the END_STREAM flag set.


  HTTP/1.1 200 OK                  HEADERS
  Content-Type: image/jpeg   ==>     - END_STREAM
  Transfer-Encoding: chunked         + END_HEADERS
  Trailer: Foo                         :status        = 200
                                       content-length = 123
  123                                  content-type   = image/jpeg
  {binary data}                        trailer        = Foo
  Foo: bar                         DATA
                                     - END_STREAM
                                   {binary data}

                                     + END_STREAM
                                     + END_HEADERS
                                       foo: bar

8.1.4 Request Reliability Mechanisms in HTTP/2 HTTP/2響應可靠性機制

In HTTP/1.1, an HTTP client is unable to retry a non-idempotent request when an error occurs, because there is no means to determine the nature of the error. It is possible that some server processing occurred prior to the error, which could result in undesirable effects if the request were reattempted.


HTTP/2 provides two mechanisms for providing a guarantee to a client that a request has not been processed:

  • The GOAWAY frame indicates the highest stream number that might have been processed. Requests on streams with higher numbers are therefore guaranteed to be safe to retry.
  • The REFUSED_STREAM error code can be included in a RST_STREAM frame to indicate that the stream is being closed prior to any processing having occurred. Any request that was sent on the reset stream can be safely retried.


  • 超時幀指示了流可能被處理的最大流流標示。在更大數字的流上的請求可以保證安全的重試。
  • RST_STREAM幀中可以包含REFUSED_STREAM錯誤碼來指示流由於之前的處理正在關閉。重置流上的任何請求都可以安全重試。

Requests that have not been processed have not failed; clients MAY automatically retry them, even those with non-idempotent methods.


A server MUST NOT indicate that a stream has not been processed unless it can guarantee that fact. If frames that are on a stream are passed to the application layer for any stream, then REFUSED_STREAM MUST NOT be used for that stream, and a GOAWAY frame MUST include a stream identifier that is greater than or equal to the given stream identifier.


In addition to these mechanisms, the PING frame provides a way for a client to easily test a connection. Connections that remain idle can become broken as some middleboxes (for instance, network address translators, or load balancers) silently discard connection bindings. The PING frame allows a client to safely test whether a connection is still active without sending a request.


8.2 Server Push 服務端推送

HTTP/2 enables a server to pre-emptively send (or "push") one or more associated responses to a client in response to a single request. This feature becomes particularly helpful when the server knows the client will need to have those responses available in order to fully process the response to the original request.


Pushing additional responses is optional, and is negotiated between individual endpoints. The SETTINGS_ENABLE_PUSH setting can be set to 0 to indicate that server push is disabled.


Because pushing responses is effectively hop-by-hop, an intermediary could receive pushed responses from the server and choose not to forward those on to the client. In other words, how to make use of the pushed responses is up to that intermediary. Equally, the intermediary might choose to push additional responses to the client, without any action taken by the server.


A client cannot push. Thus, servers MUST treat the receipt of a PUSH_PROMISE frame as a connection error (Section 5.4.1) of type PROTOCOL_ERROR. Clients MUST reject any attempt to change the SETTINGS_ENABLE_PUSH setting to a value other than 0 by treating the message as a connection error (Section 5.4.1) of type PROTOCOL_ERROR.


A server can only push responses that are cacheable (see [RFC7234], Section 3); promised requests MUST be safe (see [RFC7231], Section 4.2.1) and MUST NOT include a request body.


8.2.1 Push Requests 推送請求

Server push is semantically equivalent to a server responding to a request; however, in this case that request is also sent by the server, as a PUSH_PROMISE frame.


The PUSH_PROMISE frame includes a header block that contains a complete set of request header fields that the server attributes to the request. It is not possible to push a response to a request that includes a request body.


Pushed responses are always associated with an explicit request from the client. The PUSH_PROMISE frames sent by the server are sent on that explicit request's stream. The PUSH_PROMISE frame also includes a promised stream identifier, chosen from the stream identifiers available to the server (see Section 5.1.1).


The header fields in PUSH_PROMISE and any subsequent CONTINUATION frames MUST be a valid and complete set of request header fields (Section The server MUST include a method in the :method header field that is safe and cacheable. If a client receives a PUSH_PROMISE that does not include a complete and valid set of header fields, or the :method header field identifies a method that is not safe, it MUST respond with a stream error (Section 5.4.2) of type PROTOCOL_ERROR.


The server SHOULD send PUSH_PROMISE (Section 6.6) frames prior to sending any frames that reference the promised responses. This avoids a race where clients issue requests prior to receiving any PUSH_PROMISE frames.


For example, if the server receives a request for a document containing embedded links to multiple image files, and the server chooses to push those additional images to the client, sending push promises before the DATA frames that contain the image links ensures that the client is able to see the promises before discovering embedded links. Similarly, if the server pushes responses referenced by the header block (for instance, in Link header fields), sending the push promises before sending the header block ensures that clients do not request them.

例如:如果服務端收到文檔請求包含多個嵌入式的圖像鏈接,而且服務端選擇推送那些額外的圖像給客戶端,再數據幀前發送push promises能確保客戶端能夠在發現內嵌鏈接前看到這些承諾。類似的,如果服務端推送與報頭區塊(例如,在Link報頭域)相關的響應,再發送報頭區塊前推送承諾能確保客戶端不請求它們。

PUSH_PROMISE frames MUST NOT be sent by the client.


PUSH_PROMISE frames can be sent by the server in response to any client-initiated stream, but the stream MUST be in either the "open" or "half closed (remote)" state with respect to the server. PUSH_PROMISE frames are interspersed with the frames that comprise a response, though they cannot be interspersed with HEADERS and CONTINUATION frames that comprise a single header block.


Sending a PUSH_PROMISE frame creates a new stream and puts the stream into the “reserved (local)” state for the server and the “reserved (remote)” state for the client.


8.2.2 Push Responses 推送響應

After sending the PUSH_PROMISE frame, the server can begin delivering the pushed response as a response (Section on a server-initiated stream that uses the promised stream identifier. The server uses this stream to transmit an HTTP response, using the same sequence of frames as defined in Section 8.1. This stream becomes "half closed" to the client (Section 5.1) after the initial HEADERS frame is sent.


Once a client receives a PUSH_PROMISE frame and chooses to accept the pushed response, the client SHOULD NOT issue any requests for the promised response until after the promised stream has closed.


If the client determines, for any reason, that it does not wish to receive the pushed response from the server, or if the server takes too long to begin sending the promised response, the client can send an RST_STREAM frame, using either the CANCEL or REFUSED_STREAM codes, and referencing the pushed stream's identifier.


A client can use the SETTINGS_MAX_CONCURRENT_STREAMS setting to limit the number of responses that can be concurrently pushed by a server. Advertising a SETTINGS_MAX_CONCURRENT_STREAMS value of zero disables server push by preventing the server from creating the necessary streams. This does not prohibit a server from sending PUSH_PROMISE frames; clients need to reset any promised streams that are not wanted.


Clients receiving a pushed response MUST validate that the server is authorized to provide the response, see Section 10.1. For example, a server that offers a certificate for only the example.com DNS-ID or Common Name is not permitted to push a response for https://www.example.org/doc.


The response for a PUSH_PROMISE stream begins with a HEADERS frame, which immediately puts the stream into the “half closed (remote)” state for the server and “half closed (local)” state for the client, and ends with a frame bearing END_STREAM, which places the stream in the "closed" state.


Note:The client never sends a frame with the END_STREAM flag for a server push.


8.3 The CONNECT Method CONNECT方法

In HTTP/1.x, the pseudo-method CONNECT ([RFC7231], Section 4.3.6) is used to convert an HTTP connection into a tunnel to a remote host. CONNECT is primarily used with HTTP proxies to establish a TLS session with an origin server for the purposes of interacting with https resources.


In HTTP/2, the CONNECT method is used to establish a tunnel over a single HTTP/2 stream to a remote host, for similar purposes. The HTTP header field mapping works as mostly as defined in Request Header Fields (Section, with a few differences. Specifically:


  • The :method header field is set to CONNECT.
  • The :scheme and :path header fields MUST be omitted.
  • The :authority header field contains the host and port to connect to (equivalent to the authority-form of the request-target of CONNECT requests, see [RFC7230], Section 5.3).

  • :method是連接中包含:method報頭字段。

  • :scheme和:path報頭字段必須被忽略。
  • :authority報頭字段包含主機及連接的端口(相當於authority形式的請求目標連接請求,見RFC7230章節5.3)。

A proxy that supports CONNECT establishes a TCP connection [TCP] to the server identified in the :authority header field. Once this connection is successfully established, the proxy sends a HEADERS frame containing a 2xx series status code to the client, as defined in [RFC7231], Section 4.3.6.


After the initial HEADERS frame sent by each peer, all subsequent DATA frames correspond to data sent on the TCP connection. The payload of any DATA frames sent by the client are transmitted by the proxy to the TCP server; data received from the TCP server is assembled into DATA frames by the proxy. Frame types other than DATA or stream management frames (RST_STREAM, WINDOW_UPDATE, and PRIORITY) MUST NOT be sent on a connected stream, and MUST be treated as a stream error (Section 5.4.2) if received.


The TCP connection can be closed by either peer. The END_STREAM flag on a DATA frame is treated as being equivalent to the TCP FIN bit. A client is expected to send a DATA frame with the END_STREAM flag set after receiving a frame bearing the END_STREAM flag. A proxy that receives a DATA frame with the END_STREAM flag set sends the attached data with the FIN bit set on the last TCP segment. A proxy that receives a TCP segment with the FIN bit set sends a DATA frame with the END_STREAM flag set. Note that the final TCP segment or DATA frame could be empty.

TCP連接可以被各個對等端關閉。數據幀上的END_STREAM標記被認為與TCP FIN比特相同。客戶端在收到帶有END_STREAM標記的幀後被期望應該發送一個帶有 END_STREAM標記的數據幀。代理接收到帶有END_STREAM 標記的數據幀將在發送這些數據的時候在最後的TCP段上設置FIN位。帶有接收到帶有FIN位的TCP端發送一個帶有END_STREAM標記的數據幀。注意最後的TCP端或者數據幀可以為空。

A TCP connection error is signaled with RST_STREAM. A proxy treats any error in the TCP connection, which includes receiving a TCP segment with the RST bit set, as a stream error (Section 5.4.2) of type CONNECT_ERROR. Correspondingly, a proxy MUST send a TCP segment with the RST bit set if it detects an error with the stream or the HTTP/2 connection.


9 Additional HTTP Requirements/Considerations 額外HTTP要求/考慮

This section outlines attributes of the HTTP protocol that improve interoperability, reduce exposure to known security vulnerabilities, or reduce the potential for implementation variation.


9.1 Connection Management 連接管理

HTTP/2 connections are persistent. For best performance, it is expected clients will not close connections until it is determined that no further communication with a server is necessary (for example, when a user navigates away from a particular web page), or until the server closes the connection.


Clients SHOULD NOT open more than one HTTP/2 connection to a given host and port pair, where host is derived from a URI, a selected alternative service [ALT-SVC], or a configured proxy.


A client can create additional connections as replacements, either to replace connections that are near to exhausting the available stream identifier space (Section 5.1.1), to refresh the keying material for a TLS connection, or to replace connections that have encountered errors (Section 5.4.1).


A client MAY open multiple connections to the same IP address and TCP port using different Server Name Indication [TLS-EXT] values or to provide different TLS client certificates, but SHOULD avoid creating multiple connections with the same configuration.


Servers are encouraged to maintain open connections for as long as possible, but are permitted to terminate idle connections if necessary. When either endpoint chooses to close the transport-level TCP connection, the terminating endpoint SHOULD first send a GOAWAY (Section 6.8) frame so that both endpoints can reliably determine whether previously sent frames have been processed and gracefully complete or terminate any necessary remaining tasks.


9.1.1 Connection Reuse 復用連接

Clients MAY use a single server connection to send requests for URIs with multiple different authority components as long as the server is authoritative (Section 10.1). For http resources, this depends on the host having resolved to the same IP address.

客戶端可以使用單個服務端連接來發送多個不同認證組件的URIs請求,只要服務端是認證的(章節 10.1)。對於http資源來說,這個取決於對同個IP地址已經解析的主機端。

For https resources, connection reuse additionally depends on having a certificate that is valid for the host in the URI. That is the use of server certificate with multiple subjectAltName attributes, or names with wildcards. For example, a certificate with a subjectAltName of *.example.com might permit the use of the same connection for a.example.com and b.example.com.


In some deployments, reusing a connection for multiple origins can result in requests being directed to the wrong origin server. For example, TLS termination might be performed by a middlebox that uses the TLS Server Name Indication (SNI) [TLS-EXT] extension to select the an origin server. This means that it is possible for clients to send confidential information to servers that might not be the intended target for the request, even though the server has valid authentication credentials.


A server that does not wish clients to reuse connections can indicate that it is not authoritative for a request by sending a 421 (Not Authoritative) status code in response to the request (see Section 9.1.2).


9.1.2 The 421 (Not Authoritative) Status Code 421(未驗證)狀態碼

The 421 (Not Authoritative) status code indicates that the current origin server is not authoritative for the requested resource, in the sense of [RFC7230], Section 9.1 (see also Section 10.1).


Clients receiving a 421 (Not Authoritative) response from a server MAY retry the request - whether the request method is idempotent or not - over a different connection. This is possible if a connection is reused (Section 9.1.1) or if an alternative service is selected ([ALT-SVC]).


This status code MUST NOT be generated by proxies.


A 421 response is cacheable by default; i.e., unless otherwise indicated by the method definition or explicit cache controls (see Section 4.2.2 of [RFC7234]).

421響應緩存是默認的;舉例:除非被定義的方法或顯示的緩存控制另有說明(RFC7234, 章節4.2.2)。

9.2 Use of TLS Features 使用TLS功能

Implementations of HTTP/2 MUST support TLS 1.2 [TLS12] for HTTP/2 over TLS. The general TLS usage guidance in [TLSBCP] SHOULD be followed, with some additional restrictions that are specific to HTTP/2.

實現HTTP/2必須支持TLS 1.2。通用的TLS用法指導應該遵循,同時加上對HTTP/2的特定支持。

9.2.1 TLS Features TLS功能

The TLS implementation MUST support the Server Name Indication (SNI) [TLS-EXT] extension to TLS. HTTP/2 clients MUST indicate the target domain name when negotiating TLS.


The TLS implementation MUST disable compression. TLS compression can lead to the exposure of information that would not otherwise be revealed [RFC3749]. Generic compression is unnecessary since HTTP/2 provides compression features that are more aware of context and therefore likely to be more appropriate for use for performance, security or other reasons.


The TLS implementation MUST disable renegotiation. An endpoint MUST treat a TLS renegotiation as a connection error (Section 5.4.1) of type PROTOCOL_ERROR. Note that disabling renegotiation can result in long-lived connections becoming unusable due to limits on the number of messages the underlying cipher suite can encipher.


A client MAY use renegotiation to provide confidentiality protection for client credentials offered in the handshake, but any renegotiation MUST occur prior to sending the connection preface. A server SHOULD request a client certificate if it sees a renegotiation request immediately after establishing a connection.


This effectively prevents the use of renegotiation in response to a request for a specific protected resource. A future specification might provide a way to support this use case.


9.2.2 TLS Cipher Suites TLS加密套件

The set of TLS cipher suites that are permitted in HTTP/2 is restricted. HTTP/2 MUST only be used with cipher suites that have ephemeral key exchange, such as the ephemeral Diffie-Hellman (DHE) [TLS12] or the elliptic curve variant (ECDHE) [RFC4492]. Ephemeral key exchange MUST have a minimum size of 2048 bits for DHE or security level of 128 bits for ECDHE. Clients MUST accept DHE sizes of up to 4096 bits. HTTP MUST NOT be used with cipher suites that use stream or block ciphers. Authenticated Encryption with Additional Data (AEAD) modes, such as the Galois Counter Model (GCM) mode for AES [RFC5288] are acceptable.

HTTP/2中授權使用的TLS加密套件是不對外公開的。HTTP/2必須僅在支持密鑰交換的加密套件下使用,如短暫的Diffie-Hellman(DHE)或橢圓曲線的變體(ecdhe)。交換的密鑰必須具有最小尺寸的2048位(DHE)或128位的安全級別(ecdhe)。客戶端必須接受多達4096位DHE尺寸。HTTP絕對不能使用用流或區塊密碼的加密套件。使用額外數據(AEAD)模式的認證加密,例如針對AES[ RFC5288 ] 的Galois Counter Model (GCM)模式是允許的。

Clients MAY advertise support of other cipher suites in order to allow for connection to servers that do not support HTTP/2 to complete without the additional latency imposed by using a separate connection for fallback.


An implementation SHOULD NOT negotiate a TLS connection for HTTP/2 without also negotiating a cipher suite that meets these requirements. Due to implementation limitations, it might not be possible to fail TLS negotiation. An endpoint MUST immediately terminate an HTTP/2 connection that does not meet these minimum requirements with a connection error (Section 5.4.1) of type INADEQUATE_SECURITY.


9.3 GZip Content-Encoding 內部編碼Gzip壓縮


10 Security Considerations 安全性考慮

10.1 Server Authority 服務端認證

A client is only able to accept HTTP/2 responses from servers that are authoritative for those resources. This is particularly important for server push (Section 8.2), where the client validates the PUSH_PROMISE before accepting the response.


HTTP/2 relies on the HTTP/1.1 definition of authority for determining whether a server is authoritative in providing a given response, see [RFC7230], Section 9.1. This relies on local name resolution for the "http" URI scheme, and the authenticated server identity for the "https" scheme (see [RFC2818], Section 3).

HTTP/2依據HTTP/1.1權限定義來檢測服務端是否有權限提供給定的響應,見RFC2818 章節3.這依賴於本地“HTTP”URI方案的域名解析,以及服務端提供的“https”方案驗證。

A client MUST discard responses provided by a server that is not authoritative for those resources.


10.2 Cross-Protocol Attacks 跨協議攻擊

In a cross-protocol attack, an attacker causes a client to initiate a transaction in one protocol toward a server that understands a different protocol. An attacker might be able to cause the transaction to appear as valid transaction in the second protocol. In combination with the capabilities of the web context, this can be used to interact with poorly protected servers in private networks.


Completing a TLS handshake with an ALPN identifier for HTTP/2 can be considered sufficient protection against cross protocol attacks. ALPN provides a positive indication that a server is willing to proceed with HTTP/2, which prevents attacks on other TLS-based protocols.


The encryption in TLS makes it difficult for attackers to control the data which could be used in a cross-protocol attack on a cleartext protocol.


The cleartext version of HTTP/2 has minimal protection against cross-protocol attacks. The connection preface (Section 3.5) contains a string that is designed to confuse HTTP/1.1 servers, but no special protection is offered for other protocols. A server that is willing to ignore parts of an HTTP/1.1 request containing an Upgrade header field in addition to the client connection preface could be exposed to a cross-protocol attack.


10.3 中介端封裝攻擊

HTTP/2 header field names and values are encoded as sequences of octets with a length prefix. This enables HTTP/2 to carry any string of octets as the name or value of a header field. An intermediary that translates HTTP/2 requests or responses into HTTP/1.1 directly could permit the creation of corrupted HTTP/1.1 messages. An attacker might exploit this behavior to cause the intermediary to create HTTP/1.1 messages with illegal header fields, extra header fields, or even new messages that are entirely falsified.


Header field names or values that contain characters not permitted by HTTP/1.1, including carriage return (ASCII 0xd) or line feed (ASCII 0xa) MUST NOT be translated verbatim by an intermediary, as stipulated in [RFC7230], Section 3.2.4.


Translation from HTTP/1.x to HTTP/2 does not produce the same opportunity to an attacker. Intermediaries that perform translation to HTTP/2 MUST remove any instances of the obs-fold production from header field values.


10.4 推送響應的緩存

Pushed responses do not have an explicit request from the client; the request is provided by the server in the PUSH_PROMISE frame.


Caching responses that are pushed is possible based on the guidance provided by the origin server in the Cache-Control header field. However, this can cause issues if a single server hosts more than one tenant. For example, a server might offer multiple users each a small portion of its URI space.


Where multiple tenants share space on the same server, that server MUST ensure that tenants are not able to push representations of resources that they do not have authority over. Failure to enforce this would allow a tenant to provide a representation that would be served out of cache, overriding the actual representation that the authoritative tenant provides.


Pushed responses for which an origin server is not authoritative (see Section 10.1) are never cached or used.


10.5 拒絕服務的注意事項

An HTTP/2 connection can demand a greater commitment of resources to operate than a HTTP/1.1 connection. The use of header compression and flow control depend on a commitment of resources for storing a greater amount of state. Settings for these features ensure that memory commitments for these features are strictly bounded.


The number of PUSH_PROMISE frames is not constrained in the same fashion. A client that accepts server push SHOULD limit the number of streams it allows to be in the "reserved (remote)" state. Excessive number of server push streams can be treated as a stream error (Section 5.4.2) of type ENHANCE_YOUR_CALM.


Processing capacity cannot be guarded as effectively as state capacity.


The SETTINGS frame can be abused to cause a peer to expend additional processing time. This might be done by pointlessly changing SETTINGS parameters, setting multiple undefined parameters, or changing the same setting multiple times in the same frame. WINDOW_UPDATE or PRIORITY frames can be abused to cause an unnecessary waste of resources.

設置幀可能被濫用導致對等端花費額外的處理時間。這可能是毫無意義改變設置參數、設置多個未定義的參數,或者在同個幀中多次修改同個值。WINDOW_UPDATE 或 PRIORITY幀也可能被濫用導致資源的不必要的浪費。服務端可能在沒有權限為客戶端產生過量工作時錯誤地假定源服務器的ALTSVC幀。

Large numbers of small or empty frames can be abused to cause a peer to expend time processing frame headers. Note however that some uses are entirely legitimate, such as the sending of an empty DATA frame to end a stream.


Header compression also offers some opportunities to waste processing resources; see Section 8 of [COMPRESSION] for more details on potential abuses.


Limits in SETTINGS parameters cannot be reduced instantaneously, which leaves an endpoint exposed to behavior from a peer that could exceed the new limits. In particular, immediately after establishing a connection, limits set by a server are not known to clients and could be exceeded without being an obvious protocol violation.


All these features - i.e., SETTINGS changes, small frames, header compression - have legitimate uses. These features become a burden only when they are used unnecessarily or to excess.


An endpoint that doesn't monitor this behavior exposes itself to a risk of denial of service attack. Implementations SHOULD track the use of these features and set limits on their use. An endpoint MAY treat activity that is suspicious as a connection error (Section 5.4.1) of type ENHANCE_YOUR_CALM.


10.5.1 Limits on Header Block Size

A large header block (Section 4.3) can cause an implementation to commit a large amount of state. In servers and intermediaries, header fields that are critical to routing, such as :authority, :path, and :scheme are not guaranteed to be present early in the header block. In particular, values that are in the reference set cannot be emitted until the header block ends.

一個較大的報頭區塊(章節4.3)可以導致具體實現中提交大量的狀態。在服務端和中介端,報頭字段對路由至關重要,例如:authority, :path, 和:scheme並沒有保證在報頭區塊中靠前呈現。特別是,引用集合中的值只有在報頭區塊結束才能被提交。

This can prevent streaming of the header fields to their ultimate destination, and forces the endpoint to buffer the entire header block. Since there is no hard limit to the size of a header block, an endpoint could be forced to exhaust available memory.


A server that receives a larger header block than it is willing to handle can send an HTTP 431 (Request Header Fields Too Large) status code [RFC6585]. A client can discard responses that it cannot process. The header block MUST be processed to ensure a consistent connection state, unless the connection is closed.

服務端接收到大於它願意處理的報頭區塊可以發送一個HTTP 431(請求報頭字段過大)狀態碼 RFC6585。終端可以丟棄其不能處理的響應。報頭區塊必須被處理以確保連續的連接狀態,除非連接是關閉的。

10.6 Use of Compression

HTTP/2 enables greater use of compression for both header fields (Section 4.3) and entity bodies. Compression can allow an attacker to recover secret data when it is compressed in the same context as data under attacker control.


There are demonstrable attacks on compression that exploit the characteristics of the web (e.g., [BREACH]). The attacker induces multiple requests containing varying plaintext, observing the length of the resulting ciphertext in each, which reveals a shorter length when a guess about the secret is correct.


Implementations communicating on a secure channel MUST NOT compress content that includes both confidential and attacker-controlled data unless separate compression dictionaries are used for each source of data. Compression MUST NOT be used if the source of data cannot be reliably determined.


Further considerations regarding the compression of header fields are described in [COMPRESSION].


10.7 填充的使用

Padding within HTTP/2 is not intended as a replacement for general purpose padding, such as might be provided by TLS [TLS12]. Redundant padding could even be counterproductive. Correct application can depend on having specific knowledge of the data that is being padded.

HTTP/2的填充不打算作為通用填充的替換,如可能在TLS [TLS12]提供的。多餘的填充可能會適得其反。正確的應用依靠的是對於填充的數據有具體的認知。

To mitigate attacks that rely on compression, disabling or limiting compression might be preferable to padding as a countermeasure.


Padding can be used to obscure the exact size of frame content, and is provided to mitigate specific attacks within HTTP. For example, attacks where compressed content includes both attacker-controlled plaintext and secret data (see for example, [BREACH]).


Use of padding can result in less protection than might seem immediately obvious. At best, padding only makes it more difficult for an attacker to infer length information by increasing the number of frames an attacker has to observe. Incorrectly implemented padding schemes can be easily defeated. In particular, randomized padding with a predictable distribution provides very little protection; similarly, padding payloads to a fixed size exposes information as payload sizes cross the fixed size boundary, which could be possible if an attacker can control plaintext.


Intermediaries SHOULD retain padding for DATA frames, but MAY drop padding for HEADERS and PUSH_PROMISE frames. A valid reason for an intermediary to change the amount of padding of frames is to improve the protections that padding provides.


10.8 隱私注意事項

Several characteristics of HTTP/2 provide an observer an opportunity to correlate actions of a single client or server over time. This includes the value of settings, the manner in which flow control windows are managed, the way priorities are allocated to streams, timing of reactions to stimulus, and handling of any optional features.


As far as this creates observable differences in behavior, they could be used as a basis for fingerprinting a specific client, as defined in Section 1.8 of [HTML5].

至於這個可觀察到的行為的差異,他們可以作為特定的客戶端的識別的基礎,見HTML5 章節1.8中定義。

11 IANA Considerations

A string for identifying HTTP/2 is entered into the "Application Layer Protocol Negotiation (ALPN) Protocol IDs" registry established in [TLSALPN].

標識HTTP/2的字符串已經收錄到TLSALPN中建立的"Application Layer Protocol Negotiation (ALPN) Protocol IDs"註冊表中。

This document establishes a registry for frame types, settings, and error codes. These new registries are entered into a new "Hypertext Transfer Protocol (HTTP) 2 Parameters" section.

本文檔建立了幀類型、設置和錯誤碼的記錄。這些新的記錄被收錄到新的"Hypertext Transfer Protocol (HTTP) 2 Parameters" 章節中。

This document registers the HTTP2-Settings header field for use in HTTP; and the 421 (Not Authoritative) status code.


This document registers the PRI method for use in HTTP, to avoid collisions with the connection preface (Section 3.5).

為了避免與連接序言(章節3.5)衝突, 本文檔註冊了在HTTP中使用的PRI方法。

11.1 HTTP/2識別字符串的註冊

This document creates two registrations for the identification of HTTP/2 in the "Application Layer Protocol Negotiation (ALPN) Protocol IDs" registry established in [TLSALPN].


The "h2" string identifies HTTP/2 when used over TLS:

Protocol:HTTP/2 over TLS Identification Sequence:0x68 0x32 ("h2") Specification:This document The "h2c" string identifies HTTP/2 when used over cleartext TCP:Protocol:HTTP/2 over TCP Identification Sequence:0x68 0x32 0x63 ("h2c") Specification:This document


  • 協議: TLS上的HTTP/2
  • 標識序列 : 0x68 0x32 ("h2")
  • 定義: 本文檔
  • "h2c"字符串標識使用明文TCP時的HTTP/2: TCP上的HTTP/2
  • 協議: TCP上的HTTP/2
  • 標識序列: 0x68 0x32 0x63 ("h2c")
  • 定義: 本文檔

11.2 Frame Type Registry

This document establishes a registry for HTTP/2 frame types codes. The "HTTP/2 Frame Type" registry manages an 8-bit space. The "HTTP/2 Frame Type" registry operates under either of the "IETF Review" or "IESG Approval" policies [RFC5226] for values between 0x00 and 0xef, with values between 0xf0 and 0xff being reserved for experimental use.

本文檔建立了HTTP/2幀類型碼的註冊表。"HTTP/2 Frame Type"註冊表管理一個8位的空間。" “HTTP/2 Frame Type” 註冊表在 “IETF Review” 或者 “IESG Approval”政策下操作0x00 到 0xef的值, 0xf0 到 0xff的值是預留給實驗用的。

New entries in this registry require the following information:

Frame Type:A name or label for the frame type. Code:The 8-bit code assigned to the frame type. Specification:A reference to a specification that includes a description of the frame layout, it's semantics and flags that the frame type uses, including any parts of the frame that are conditionally present based on the value of flags.


  • 幀類型:幀類型的名稱或者標記
  • 編碼:幀類型的8位編碼標識
  • 定義:包含幀使用的佈局、語義及標記的描述的定義參考規範,包含任何幀根據標記值有條件呈現的部分。

The entries in the following table are registered by this document.


Frame TypeCodeSection
DATA0x0Section 6.1
HEADERS0x1Section 6.2
PRIORITY0x2Section 6.3
RST_STREAM0x3Section 6.4
SETTINGS0x4Section 6.5
PUSH_PROMISE0x5Section 6.6
PING0x6Section 6.7
GOAWAY0x7Section 6.8
WINDOW_UPDATE0x8Section 6.9
CONTINUATION0x9Section 6.10

11.3 Settings Registry

This document establishes a registry for HTTP/2 settings. The "HTTP/2 Settings" registry manages a 16-bit space. The "HTTP/2 Settings" registry operates under the "Expert Review" policy [RFC5226] for values in the range from 0x0000 to 0xefff, with values between and 0xf000 and 0xffff being reserved for experimental use.

本文檔為HTTP/2設置建立了註冊表。"HTTP/2 Settings"註冊表管理了一個16位的空間。"HTTP/2 Settings"註冊表在"Expert Review"政策(RFC5226)下操作0x0000 到 0xefff的值,0xf000 到 0xffff的值是為實驗保留的。

New registrations are advised to provide the following information:

  • Name:A symbolic name for the setting. Specifying a setting name is optional.
  • Code:The 16-bit code assigned to the setting.
  • Initial Value:An initial value for the setting.
  • Specification:A stable reference to a specification that describes the use of the setting.


  • 名稱 : 設置的語義名稱。定義一個設置的名稱是可選的
  • 代碼: 16位的指定設置的編碼
  • 初始值: 設置的初始值
  • 說明:描述設置使用的穩定的參考定義

An initial set of setting registrations can be found in Section 6.5.2.


NameCodeInitial ValueSpecification
HEADER_TABLE_SIZE0x14096Section 6.5.2
ENABLE_PUSH0x21Section 6.5.2
MAX_CONCURRENT_STREAMS0x3(infinite)Section 6.5.2
INITIAL_WINDOW_SIZE0x465535Section 6.5.2

11.4 錯誤碼註冊

This document establishes a registry for HTTP/2 error codes. The "HTTP/2 Error Code" registry manages a 32-bit space. The "HTTP/2 Error Code" registry operates under the "Expert Review" policy [RFC5226].


Registrations for error codes are required to include a description of the error code. An expert reviewer is advised to examine new registrations for possible duplication with existing error codes. Use of existing registrations is to be encouraged, but not mandated.


New registrations are advised to provide the following information:

  • Name:A name for the error code. Specifying an error code name is optional.
  • Code:The 32-bit error code value.
  • Description:A brief description of the error code semantics, longer if no detailed specification is provided.
  • Specification:An optional reference for a specification that defines the error code.

The entries in the following table are registered by this document.


  • 錯誤碼:32位錯誤碼值
  • 名稱: 錯誤碼名稱。指定一個錯誤碼的名稱是可選的。
  • 描述: 描述錯誤碼的適用條件
  • 規範: 定義錯誤碼規範的可選參考。


NO_ERROR0x0Graceful shutdownSection 7
PROTOCOL_ERROR0x1Protocol error detectedSection 7
INTERNAL_ERROR0x2Implementation faultSection 7
FLOW_CONTROL_ERROR0x3Flow control limits exceededSection 7
SETTINGS_TIMEOUT0x4Settings not acknowledgedSection 7
STREAM_CLOSED0x5Frame received for closed streamSection 7
FRAME_SIZE_ERROR0x6Frame size incorrectSection 7
REFUSED_STREAM0x7Stream not processedSection 7
CANCEL0x8Stream cancelledSection 7
COMPRESSION_ERROR0x9Compression state not updatedSection 7
CONNECT_ERROR0xaTCP connection error for CONNECT methodSection 7
ENHANCE_YOUR_CALM0xbProcessing capacity exceededSection 7
INADEQUATE_SECURITY0xcNegotiated TLS parameters not acceptableSection 7

11.5 HTTP2設置報頭字段註冊

This section registers the HTTP2-Settings header field in the Permanent Message Header Field Registry [BCP90].

  • Header field name:HTTP2-Settings
  • Applicable protocol:http
  • Status:standard
  • Author/Change controller:IETF
  • Specification document(s):Section 3.2.1 of this document
  • Related information:This header field is only used by an HTTP/2 client for Upgrade-based negotiation.


  • 報頭字段名稱: HTTP2-Settings
  • 應用層協議: http
  • 狀態: 標準
  • 作者/修改操作者:LETF
  • 文檔定義: 本文檔3.2.1章節
  • 相關信息: 本字段只在HTTP/2客戶端基於升級的協商中使用。

11.6 PRI方法註冊

This section registers the PRI method in the HTTP Method Registry ([RFC7231], Section 8.1).

Method Name:PRI Safe : No Idempotent : No Specification document(s) : Section 3.5 of this document Related information: This method is never used by an actual client. This method will appear to be used when an HTTP/1.1 server or intermediary attempts to parse an HTTP/2 connection preface.


  • 方法名稱 : PRI
  • - 安全: 否
  • 冪等元 : 否
  • 文檔定義: 本文檔3.5章節
  • 相關信息: 這個方法從不會被確切的客戶端使用。該方法只在HTTP/1.1服務端或者中介端試圖解析HTTP/2連接序言中使用。

11.7 The 421 Not Authoritative HTTP Status Code

This document registers the 421 (Not Authoritative) HTTP Status code in the Hypertext Transfer Protocol (HTTP) Status Code Registry ([RFC7231], Section 8.2).

  • Status Code:421
  • Short Description: Not Authoritative
  • Specification: Section 9.1.2 of this document

本文檔在Hypertext Transfer Protocol (HTTP)狀態碼註冊表(RFC7231,見章節8.2)中註冊了HTTP 421(未驗證)狀態碼。

  • 狀態碼:421
  • 簡短描述: 未驗證權限
  • 定義: 本文檔章節9.1.2

12. Acknowledgements

This document includes substantial input from the following individuals:


  • Adam Langley, Wan-Teh Chang, Jim Morrison, Mark Nottingham, Alyssa Wilk, Costin Manolache, William Chan, Vitaliy Lvin, Joe Chan, Adam Barth, Ryan Hamilton, Gavin Peters, Kent Alstad, Kevin Lindsay, Paul Amer, Fan Yang, Jonathan Leighton (SPDY contributors).
  • Gabriel Montenegro and Willy Tarreau (Upgrade mechanism).
  • William Chan, Salvatore Loreto, Osama Mazahir, Gabriel Montenegro, Jitu Padhye, Roberto Peon, Rob Trace (Flow control).
  • Mike Bishop (Extensibility).
  • Mark Nottingham, Julian Reschke, James Snell, Jeff Pinner, Mike Bishop, Herve Ruellan (Substantial editorial contributions).
  • Alexey Melnikov was an editor of this document during 2013.
  • A substantial proportion of Martin's contribution was supported by Microsoft during his employment there.



Please publish modules in offcanvas position.