HTTP/2 - The future of the web today
summary
HTTP/2 replaces many HTTP/1.x hacks by sending multiple multiplexed streams over one TCP connection per origin, using a binary framing layer and HPACK header compression to cut header bytes; real sites drop single-transaction connections from ~74% to ~25%. Server push lets servers proactively send critical assets but push caches are tied to the connection, can be consumed only once, and misused pushes hurt performance. Tooling: Chrome internals, WebPageTest, Wireshark with SSL key log and Fiddler. Expect ~20–30% speedups; QUIC/h3 next to fix TCP-level head‑of‑line.
AI-written summary · about
chapters (18)
- 0:00Introduction to HTTP/2
- 2:01Understanding protocol layers
- 4:44Bandwidth vs. latency
- 6:06History of HTTP
- 10:14Limitations of HTTP/1.1
- 13:42Workarounds and challenges
- 17:12Resource optimization hacks
- 26:29SPDY and HTTP/2 adoption
- 29:47Binary framing and multiplexing
- 33:43Stream prioritization
- 35:50The role of HTTPS
- 40:26Header compression with HPACK
- 42:58Server push functionality
- 48:10Push gotchas and trade-offs
- 51:07Universal performance tips
- 53:05Debugging tools
- 54:14Future directions and conclusion
- 56:37Q&A session
