HTTP协议解密

HTTP/1.1

HTTP/2 ([HTTP/2]) introduced a binary framing and multiplexing layer to improve latency without modifying the transport layer.

The Real Problems with HTTP/2
- server push doesn’t really work in practice
- streams and prioritization are often badly implemented
TCP is the main protocol that provides crucial services such as reliability and in-order delivery to other protocols such as HTTP.
The downside of TCP
- QUIC is needed because TCP, which has been around since the early days of the Internet, was not really built with maximum efficiency in mind.
- TCP also takes a full network round trip to complete before anything else can be done on a connection.
- TCP sees all of the data it transports as a single “file” or byte stream, even if we’re actually using it to transfer several files at the same time.

QUIC is a generic transport protocol (much like TCP)
QUIC 本可以替代 TCP，成为新一代的基础协议；但因为现存的绝大部分互联网设备基本上不会动态更新，导致新的协议很难推广，于是才利用起已知的 UDP 协议，封装成了上层协议
We can call QUIC as TCP/2 (a much advanced version of TCP)