HTTP
The Hypertext Transfer Protocol (HTTP) is an application-level protocol for distributed, collaborative, hypermedia information systems.
bing.com 翻譯：
超文字傳輸協議 （HTTP） 是用於分散式的、協作的、超媒體資訊系統的 應用程式級協議。
IETF
Internet Engineering Task Force (IETF)
HTTP/1.0
Hypertext Transfer Protocol -- HTTP/1.0
RFC 文件：
https://www.rfc-editor.org/rfc/rfc1945
INFORMATIONAL (May 1996)
HTTP/1.1
Hypertext Transfer Protocol -- HTTP/1.1
RFC 文件：
https://www.rfc-editor.org/rfc/rfc2068
PROPOSED STANDARD
https://www.rfc-editor.org/rfc/rfc2616
DRAFT STANDARD (June 1999)
Upgrading to TLS Within HTTP/1.1
https://www.rfc-editor.org/rfc/rfc2817
PROPOSED STANDARD
This memo explains how to use the Upgrade mechanism in HTTP/1.1 to initiate Transport Layer Security (TLS) over an existing TCP connection.
MDN-HTTP
https://developer.mozilla.org/zh-CN/docs/Web/HTTP
|
超文字傳輸協議（HTTP）是一個用於傳輸超媒體文件（例如 HTML）的應用層協議。 它是為 Web 瀏覽器與 Web 伺服器之間的通訊而設計的，但也可以用於其他目的。 HTTP 遵循經典的客戶端—服務端模型，客戶端開啟一個連線以發出請求，然後等待直到收到伺服器端響應。 HTTP 是無狀態協議，這意味著伺服器不會在兩個請求之間保留任何資料（狀態）。 |
HTTP/2.0
Hypertext Transfer Protocol Version 2 (HTTP/2)
RFC 文件：
https://www.rfc-editor.org/rfc/rfc7540
PROPOSED STANDARD (May 2015)
|
HTTP/2 enables a more efficient use of network It also introduces unsolicited push of |
|
bing.com 翻譯： HTTP/2 透過引入 標頭欄位壓縮 並 允許在同一連線上進行多個併發交換，可以更有效地使用網路資源並減少延遲感知。 它還引入了 從伺服器到客戶端的主動推送 表示。 |
Using TLS 1.3 with HTTP/2
https://www.rfc-editor.org/rfc/rfc8740
Status: Proposed Standard (February 2020)
RFC 9113 HTTP/2
https://www.rfc-editor.org/rfc/rfc9113
Status: Proposed Standard (June 2022)
怎麼又來一個 HTTP/2？
Obsoletes:7540, 8740.
| This specification describes an optimized expression of the semantics of the Hypertext Transfer Protocol (HTTP), referred to as HTTP version 2 (HTTP/2). |
|
bing.com 翻譯： 本規範描述了超文字傳輸協議 （HTTP） 語義的最佳化表示式，稱為 HTTP 版本 2 （HTTP/2）。 |
MDN-HTTP/2
https://developer.mozilla.org/zh-CN/docs/Glossary/HTTP_2
|
HTTP/2 是 HTTP 網路協議的一個重要版本。 HTTP / 2 的主要目標是透過啟用完整的請求和響應多路複用來減少 延遲，透過有效壓縮 HTTP 標頭欄位來最小化協議開銷，並增加對請求優先順序和伺服器推送的支援。 |
gRPC
A high performance, open source universal RPC framework
https://grpc.io
| Why gRPC? gRPC is a modern open source high performance Remote Procedure Call (RPC) framework that can run in any environment. It can efficiently connect services in and across data centers with pluggable support for load balancing, tracing, health checking and authentication. It is also applicable in last mile of distributed computing to connect devices, mobile applications and browsers to backend services. |
和 HTTP/2 的關係：
|
Bi-directional streaming and integrated auth. Bi-directional streaming and fully integrated pluggable authentication with HTTP/2-based transport. |
FAQ: 搜尋 HTTP
https://grpc.io/docs/what-is-grpc/faq/
--
文章：
gRPC on HTTP/2 Engineering a Robust, High-performance Protocol
https://grpc.io/blog/grpc-on-http2/
By Jean de Klerk (Google) | Monday, August 20, 2018
HTTP/3
RFC 9114 HTTP/3
https://www.rfc-editor.org/rfc/rfc9114.html
Status: Proposed Standard (June 2022)
|
Abstract The QUIC transport protocol has several features that are desirable in a transport for HTTP, such as stream multiplexing, per-stream flow control, and low-latency connection establishment. This document describes a mapping of HTTP semantics over QUIC. This document also identifies HTTP/2 features that are subsumed by QUIC and describes how HTTP/2 extensions can be ported to HTTP/3. |
|
bing.com 翻譯： 摘要 QUIC 傳輸協議 具有 HTTP 傳輸中所需的幾個功能， 例如流多路複用、每流流量控制和低延遲連線建立。 本文件介紹QUIC上的HTTP語義對映。 本文件還標識了 QUIC 包含的 HTTP/2 功能，並描述瞭如何將 HTTP/2 擴充套件移植到 HTTP/3。 |
RFC 9000 QUIC
QUIC: A UDP-Based Multiplexed and Secure Transport
https://www.rfc-editor.org/rfc/rfc9000.html
Status: Proposed Standard (May 2021)
|
Abstract This document defines the core of the QUIC transport protocol. QUIC provides applications with flow-controlled streams for structured communication, low-latency connection establishment, and network path migration. QUIC includes security measures that ensure confidentiality, integrity, and availability in a range of deployment circumstances. Accompanying documents describe the integration of TLS for key negotiation, loss detection, and an exemplary congestion control algorithm. |
|
bing.com 翻譯： 摘要 本文件定義了 QUIC 傳輸協議的核心。 QUIC 為應用程式提供流控制流，用於結構化通訊、低延遲連線建立和網路路徑遷移。 QUIC 包括確保在各種部署情況下的機密性、完整性和可用性的安全措施。 隨附的文件描述了用於金鑰協商、丟失檢測和示例性擁塞控制演算法的 TLS 整合。 |
The quic-go Protocol Suite
https://quic-go.net/docs/
| quic-go is a general-purpose implementation of the QUIC protocol (RFC 9000, RFC 9001, RFC 9002) in Go. |
|
quic-go also has support for HTTP/3 (RFC 9114), including QPACK (RFC 9204) and HTTP Datagrams (RFC 9297). With this package, it is possible to run a Go server that serves HTTP/1.1, HTTP/2 and HTTP/3. |
開發者：Marten Seemann
https://github.com/sponsors/marten-seemann
一些文章
深入解讀HTTP3的原理及應用 - 方圓的文章 - 知乎
https://zhuanlan.zhihu.com/p/140739394
編輯於 2020-05-14 10:50
QUIC 協議詳解 - 騰訊技術工程的文章 - 知乎
https://zhuanlan.zhihu.com/p/405387352
釋出於 2021-08-31 14:32
由 Google 自研，2012 年部署上線，2013 年提交 IETF，2021 年 5 月，IETF 推出標準版 RFC9000。
END.
本文連結：
https://www.cnblogs.com/luo630/p/18176377
ben釋出於部落格園
ben釋出於部落格園