HTTP 2.0 from the Developer's Viewpoint
summary
HTTP/2 is already widely supported (browsers and most CDNs; notable gaps: Opera Mini, UC Browser and some Chinese networks) and gives measurable wins — EngineX tests show HTTP/2 beats HTTP/1.1 over TLS and doubles throughput under latencies <300ms, and a simple server push example cuts load time by ~60%. Key changes: HPACK header compression replaces repeated big User-Agent headers, avoid domain sharding and big single bundles, use a core‑and‑more strategy, enable server push carefully and always A/B test.
AI-written summary · about
chapters (43)
- 0:00Intro
- 0:13Upgrade to HTTP 20
- 1:19Supported Browsers
- 1:47HTTP 20 Standardized
- 3:54TLS Security
- 4:40Big Sites
- 5:26Why HTTP
- 6:44Binary protocol
- 7:03Telnet
- 10:08User Agent
- 11:08HPAC Compression
- 12:45Software Development Rules
- 14:20Domain Sharding
- 16:06Two is too many
- 16:39Use all the bandwidth
- 17:14H2 has a solution
- 18:09Cookie list domains
- 18:50Serverside script combining
- 19:35What happens when files change
- 20:18Combining files
- 20:38Core Then More
- 22:07Benchmarks
- 23:15Server Push
- 25:37Bloom Filter
- 26:41Cat
- 26:51Browser
- 28:04Leaders
- 28:44Best H2 Performance
- 30:48I did everything to make it fast
- 30:59Chrome
- 31:38Firefox
- 32:10HTTP 2 Speedy Indicator
- 32:25HTTP 2 Speedy Example
- 32:43HTTP 1 Speedy Example
- 33:08Testing
- 35:04Questions
- 35:27Resources
- 36:16Fewer Connections
- 38:28Other Questions
- 40:39Negative Thoughts
- 43:56Flow Control
- 45:16One connection
- 45:34One connection per server
