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

Re: Additional HTTP Status Codes - "Request Too Onerous"

From: Alexander Dutton <alexander.dutton@oucs.ox.ac.uk>
Date: Wed, 09 Nov 2011 23:22:38 +0000
Message-ID: <4EBB0B3E.1040906@oucs.ox.ac.uk>
To: Sam Johnston <samj@samj.net>
CC: "ietf-http-wg@w3.org" <ietf-http-wg@w3.org>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 09/11/11 16:19, Sam Johnston wrote:
> Is it the client's fault for making onerous requests though, or
> the server's for being unable or unwilling to satisfy them? I'm
> more inclined to think that this is a server (5xx) issue.

As Andy Seaborne points out in a post to another mailing list┬╣, RFC
2616 says that 5xx codes "indicate cases in which the server is aware
that it has erred or is incapable of performing the request". Hence, a
5xx code would seem to fit (unless one differentiates between
"incapable" and "unwilling").

Still, I'm not sure; it's equally easy to say argue that the client is
being unreasonable in its demands.

Yours,

Alex

┬╣ <http://lists.w3.org/Archives/Public/public-lod/2011Apr/0268.html>

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAk67CzcACgkQS0pRIabRbjAhCQCffzBWvb4olmOshlm1BoJLJEn9
j5QAn1blaH+NyxRd0nJApaWgz+KKzJZk
=HH+7
-----END PGP SIGNATURE-----
Received on Wednesday, 9 November 2011 23:23:07 GMT

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