February 18th, 2015. A day that, for better or worse, will change the internet.
The IESG has formally approved the HTTP/2 and HPACK specifications, and they’re on their way to the RFC Editor, where they’ll soon be assigned RFC numbers, go through some editorial processes, and be published.
This means HTTP/2 has been finalised and the spec is ready to be implemented.
Here are a few things to read up on, in case you’re new to the HTTP/2 protocol.
- What you should change as a developer: Architecting Websites for the HTTP/2 Era
- Should we expect speed improvements in HTTP/2: does HTTP/2 or SPDY actually improve performance?
- Server Side Push benefits: the performance gains we can expect from HTTP/2 Server Side Push?
I for one am happy to see HTTP/2 be finalised. There are some really good parts about the spec. Yes, it’s lacking in some areas – but it’s by far an improvement over the HTTP/1.1 spec.