With Great Power Comes Great Responsibility - Using HTTP/2 Responsibly
summary
HTTP/2 keeps HTTP/1 semantics but forces HTTPS and replaces parallel connections with multiplexing over a single TCP stream, which improves latency but collapses everything on packet loss (lab tests show HTTP/2 degrades more than HTTP/1 under loss). Header compression via HPACK dynamic table can waste CPU and memory with changing cookies. Practical experiments build server push into ASP.NET MVC (HTML helper failed; server push via action filters succeeds) and use service-worker cache digests to avoid useless pushes. QUIC/HTTP3 and cache-aware push are the long‑term fixes.
AI-written summary · about
chapters (15)
- 0:00Introduction
- 0:24HTTP2 History
- 3:56Can I use HTTP2
- 5:22How HTTP2 works
- 8:05Packet loss
- 9:43Hpack
- 14:05Sprites
- 19:36Content Delivery Networks
- 20:51Server Push
- 24:22When to Push
- 27:32Service Workers
- 30:03Protocol Based Content Delivery
- 31:08Reverse Proxy
- 34:03Our Hands
- 36:36Quick
