1
HTTP/2 Is Done
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.
Mark Nottingham
Mark Nottingham's home page
- Popular posts
- 17
- Total points
- 3,228
- HN comments
- 1,403
- Rank
- #434 personal
Visit mnot.net → RSS feedOn Hacker News May 2011 – Jul 2026
Networking & Internet 12Web & Frontend 9Society, Policy & Culture 7Systems & Performance 3Security & Privacy 1Life, Learning & Writing 1
2
Server-sent events, WebSockets, and HTTP
The orange site is currently discussing an article about Server-Sent Events, especially as compared with WebSockets (and the emerging WebTransport). Both the article and discussion are well-informed, but I think they miss out on one aspect that has fairly deep implications.
3
What will a Chromium-only Web look like?
Most of the complexity and nuance of the Web is stuffed into browser engines. Even though they’re a huge burden to develop and maintain, the world is lucky enough to have three major ones, and they’re all Open Source.
4
RFC 2616 is dead
Don’t use RFC 2616. Delete it from your hard drives, bookmarks, and burn (or responsibly recycle) any copies that are printed out.
5
Apple's HTTP POST caching is a bug
One of the changes in Apple’s release of iOS6 last week was a surprising new ability to cache POST responses.
6
Will there be a Distributed HTTP?
One of the things that came up at the HTTP Workshop was “distributed HTTP” — i.e., moving the Web from a client/server model to a more distributed one. This week, Brewster Khale (of Archive.org fame) talked about similar thoughts on his blog and at CCC. If you haven’t seen that yet, I’d highly suggest watching the…
7
So You Want to Define a Well-Known URI
When to reach for a well-known URI — and the traps that catch most protocol designers.
8
Designing Headers for HTTP Compression
One of the concerns that often comes up when someone creates a new HTTP header is how much “bloat” it will add on the network. This is especially relevant in requests, when a little bit of extra data can introduce a lot of latency when repeated on every request.
9
On HTTP Load Testing
A lot of people seem to be talking about and performing load tests on HTTP servers, perhaps because there’s a lot more choice of servers these days.