W3C home > Mailing lists > Public > ietf-http-wg@w3.org > April to June 2013

Re: Status code 451 adoption

From: Mark Nottingham <mnot@mnot.net>
Date: Wed, 17 Apr 2013 12:05:45 +1000
Cc: Stephane Bortzmeyer <bortzmeyer@nic.fr>, "ietf-http-wg@w3.org" <ietf-http-wg@w3.org>
Message-Id: <15ACDF78-52A9-424F-B076-8CDB8B108EA4@mnot.net>
To: Tim Bray <tbray@textuality.com>

On 17/04/2013, at 1:56 AM, Tim Bray <tbray@textuality.com> wrote:

> Also, the implementer wrote a follow-up on his blog:
> http://agmweb.ca/2013-04-13-http-status-codes/

At the end, they write:

> Unfortunately some of these status codes are a little less well defined. For code 451 there are currently at least 3 proposed meanings:something about users mailboxes and something RTSP along with the legal restriction. But hopefully users of our API will realise we aren't using Exchange or RTSP

Exchange didn't register, so that's their luck. HTTP isn't RTSP, so that's not a worry.

> and maybe even read the docs to find out what this means.

The whole point of a HTTP status code is that you *don't* have to read application-specific documentation to figure out what it means.


Mark Nottingham   http://www.mnot.net/
Received on Wednesday, 17 April 2013 02:06:17 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 1 March 2016 11:11:12 UTC