o m e / p a t h / t o / c o n t e n t H T T P / 1 . 1 H o s t : w w w . s o m e h o s t . c o m A c c e p t : t e x t / h t m l A c c e p t - L a n g u a g e : e n - u s A c c e p t - E n c o d i n g : g z i p , d e f l a t e U s e r - A g e n t : M o z i l l a / 5 . 0 ( M a c i n t o s h ; I n t e l M a c O S X 1 0 _ 8 _ 3 ) A p p l e W e b K i t / 5 3 7 . 3 1 ( C o n n e c t i o n : K e e p - A l i v e C o n t e n t - L e n g t h : 2 0 M a y b e s o m e b o d y h e r e
(option for 1.0 Http 1.1: Pipelining (not good enough, maybe not even used) Browsers: 6-8 max concurrent connections per server Think of 1mb of data split 1, 10, 100 ways cache-control Minimize connections (sprites, minification, domain sharding)
to upgrade to SPDY) HTTP semantics do not change Support for node.js (node-spdy), NGINX, Apache HTTP 2.0 will be largerly based on SPDY http://dev.chromium.org/spdy