HTTP/2 : What you need to know
summary
HTTP/2 replaces text framing with a binary protocol that multiplexes many requests over a single TCP connection, eliminates HTTP/1.1 head‑of‑line blocking for same‑host requests, and adds header compression (HPACK) plus stream prioritization and optional server push. Real deployments (SPDY → HTTP/2) show 5–15% typical gains but much larger wins on high‑latency, many‑request pages; failures occur if servers or middleboxes mishandle it. Fiddler today downgrades HTTP/2 traffic; use Wireshark or browser indicators and test before changing bundling, sprites, or sharding strategies.
AI-written summary · about
chapters (28)
- 0:00Introduction
- 0:41HTTP
- 1:18RFC
- 1:53HTTP111
- 2:45Fiddler
- 4:22Problems with HTTP
- 5:45Multiple connections
- 6:52Headofline blocking
- 10:07verbose headers
- 10:49bandwidth
- 11:07latency
- 11:33bandwidth vs latency
- 13:02Google
- 16:15HTTP Goals
- 18:41Frame Types
- 19:06Streams
- 22:04Single Connection
- 23:43Header Compression
- 27:22Server Push
- 35:13Expectations
- 36:52Performance techniques
- 42:00Three golden rules
- 45:42My strategy
- 47:58Detect protocol version
- 48:56Summary
- 49:35Resources
- 50:16Questions
- 57:44Wrapup
