Whirlwind tour through the HTTP2 spec
summary
HTTP/2 is finalized in 2016 and already carries about 22% of internet traffic roughly 35% of HTTPS; a binary, multiplexed protocol replaces many TCP connections with streams and frames so browsers can reprioritize and avoid head‑of‑line blocking. Live demos use nghttp client and Google's h2 server, and a tiled image test shows multiplexing actually speeds rendering. Server push and HPACK Huffman headers appear practical. Enabling on servers is tiny (nginx config is a five‑character change), but writing app‑level push needs new app–server APIs.
AI-written summary · about
chapters (17)
- 0:00Intro
- 1:56IS HTTP/2 MADE BY GOOGLE?
- 2:29ARE HEADERS COMPRESSED?
- 10:37CONNECTIONS 38 PAGE
- 10:50REQUEST BONANZA
- 16:20HOL* BLOCKING RECAP
- 18:03PRELOADING HACKS!
- 20:14HTTP/1.1 101 Switching Protocols Connection: Upgrade Upgrade: h2c
- 28:34HTTP/2 FEATURES
- 39:03HUFFMAN IN 1 MINUTE
- 41:59HTTP/2 IN THE REAL WORLD
- 52:00YOU ARE HOLDING IT WRONG
- 54:08STOP CONCATENATING
- 54:52STOP SPRITING
- 55:03STOP DOMAIN SHARDING
- 55:30TRASH THE ASSET PIPELINE
- 56:04START USING HTTP/2
