W3C home > Mailing lists > Public > ietf-http-wg@w3.org > October to December 2011

Additional HTTP Status Codes - "Request Too Onerous"

From: Alexander Dutton <alexander.dutton@oucs.ox.ac.uk>
Date: Wed, 09 Nov 2011 15:38:46 +0000
Message-ID: <4EBA9E86.8030803@oucs.ox.ac.uk>
To: ietf-http-wg@w3.org

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi all,

Apologies if I'm speaking out of turn, but is there a case to be made
for a "Request Too Onerous" status code to be included in the draft[1]?

There are occasions where a web service might want to dissuade user
agents from:

a) requesting too large a response (e.g. tell me everything you know)
b) requesting too much computation (e.g. solve this Travelling
Salesman Problem for more nodes than is tractable)

In each case a client would know that a simpler request is more likely
to succeed. As far as I can tell, the use case is not covered by any
other status code (not 400 as the request is well-formed; not 500 as
the server didn't break; not 503 as there's no expectation that the
request might be serviceable at a later date).

This would complement the proposed 429 Too Many Requests, covering the
other case where one might want to tame over-demanding clients.

Kind regards,

Alexander

[1] http://tools.ietf.org/html/draft-nottingham-http-new-status-03

- -- 
Alexander Dutton
Developer, InfoDev, data.ox.ac.uk, OxPoints
Oxford University Computing Services, ℡ 01865 (6)13483
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org/

iEYEARECAAYFAk66noYACgkQS0pRIabRbjArFQCfbrScrb3TPptG1gNKaTymsWPh
DDYAn1OYAO0f0xiLEJOoZNvwZ3ohQbsY
=UwuN
-----END PGP SIGNATURE-----
Received on Wednesday, 9 November 2011 15:39:12 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Friday, 27 April 2012 06:51:50 GMT