New HTTP Codes

Summary:<p><pre><code> 428 Precondition Required 429 Too Many Requests 431 Request Header Fields Too Large 511 Network Authentication Required </code></pre> I've been using <i>414 Request-URI Too Long</i> for 431 and <i>503 Service Temporarily Unavailable</i> for 429

These all seem immediately practical status codes that add semantics I've been wanting. Great! In particular I am happy about the 429 Too Many Requests header, as every time I've done rate throttling I've had to quibble over what code to actually send back.

A bit offtopic, but does anybody know what typesetting system was used to produce this document? It looks like troff manpages. Is that what is used for RFC documents as well? I love the oldschool look of it.

I wish HTTP requests submitted time zone information.

511 seems a little pointless -- browsers can treat it differently, but if the intermediate gateway intends to be malicious, then it won't return 511 anyway. The only useful thing I can see is avoiding accidents/attacks on the gateway compromising its clients.

Isn't this something that the http server handles? I am not in web development except for basic php and cgi scripts. Are people actually writing web app code to dictate what http code comes back on each request?

Whelp I guess this needs updating now, <a href="https://github.com/basho/webmachine/raw/master/docs/http-headers-status-v3.png" rel="nofollow">https://github.com/basho/webmachine/raw/master/docs/http-hea...</a>

Today I learned about If-Match. 428 Precondition Required looks great!

429 looks to me as if it might be addressing aggressive http pipelining, but I was under the impression that most browsers have pipelining turned off.

Shouldn't 429 (Too many requests) be a 5xx code?

One quibble. Perhaps I don't quite get the philosophy behind these, but wouldn't it be more useful to have a uniform structure to the responses. E.g., how useful is it to the average user to get a human-readable response for 428 when it's likely to be consumed by an app (i.e., JS) which would have to parse the suggested &#60;p&#62; tag?

429 Too Many Requests is really great for APIs, hopefully http clients start supporting this.

428 seems interesting as a way to serialize objects and store them client-side, but assure the version stays consistent with the server. Or am I overthinking it?

Can't wait to set browser dependent status codes :-D

Can I start using any of these codes right now? It looks like this is still a draft. Thanks!

What happened to 430?

511: 'Unknown clients then have all traffic blocked, except for that on TCP port 80, which is sent to a HTTP server (the "login server") dedicated to "logging in" unknown clients, and of course traffic to the login server itself.'<p>Ugh. Couldn't this be more generic?

OMG really? Do we want to make HTTP even bigger? Don't we want to dump it for good and look for something more suitable to what the modern web needs instead?