Re: Status code 451 adoption
Mark Nottingham <mnot@mnot.net> Wed, 17 April 2013 02:06 UTC
Return-Path: <ietf-http-wg-request@listhub.w3.org>
X-Original-To: ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com
Delivered-To: ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 30CBC21F9757 for <ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com>; Tue, 16 Apr 2013 19:06:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.037
X-Spam-Level:
X-Spam-Status: No, score=-9.037 tagged_above=-999 required=5 tests=[AWL=1.562, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ysQlcDcmbmUr for <ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com>; Tue, 16 Apr 2013 19:06:37 -0700 (PDT)
Received: from frink.w3.org (frink.w3.org [128.30.52.56]) by ietfa.amsl.com (Postfix) with ESMTP id D744321F9743 for <httpbisa-archive-bis2Juki@lists.ietf.org>; Tue, 16 Apr 2013 19:06:36 -0700 (PDT)
Received: from lists by frink.w3.org with local (Exim 4.72) (envelope-from <ietf-http-wg-request@listhub.w3.org>) id 1USHlL-0004tj-Qy for ietf-http-wg-dist@listhub.w3.org; Wed, 17 Apr 2013 02:06:19 +0000
Resent-Date: Wed, 17 Apr 2013 02:06:19 +0000
Resent-Message-Id: <E1USHlL-0004tj-Qy@frink.w3.org>
Received: from maggie.w3.org ([128.30.52.39]) by frink.w3.org with esmtp (Exim 4.72) (envelope-from <mnot@mnot.net>) id 1USHlJ-0004t4-Ky for ietf-http-wg@listhub.w3.org; Wed, 17 Apr 2013 02:06:17 +0000
Received: from mxout-07.mxes.net ([216.86.168.182]) by maggie.w3.org with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.72) (envelope-from <mnot@mnot.net>) id 1USHlI-0001RC-Kk for ietf-http-wg@w3.org; Wed, 17 Apr 2013 02:06:17 +0000
Received: from [192.168.1.80] (unknown [118.209.210.200]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by smtp.mxes.net (Postfix) with ESMTPSA id 42F7222E257; Tue, 16 Apr 2013 22:05:48 -0400 (EDT)
Content-Type: text/plain; charset="iso-8859-1"
Mime-Version: 1.0 (Mac OS X Mail 6.3 \(1503\))
From: Mark Nottingham <mnot@mnot.net>
In-Reply-To: <CAHBU6itK-FznB_OE5qzZJKM0QFPtbGdQZVQFb29fwrNpJfDq3w@mail.gmail.com>
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>
Content-Transfer-Encoding: quoted-printable
Message-Id: <15ACDF78-52A9-424F-B076-8CDB8B108EA4@mnot.net>
References: <CAHBU6ityXJne5SbaUXo1hyLrKe43bU3ejVOMN7Tu=tS72h1bAQ@mail.gmail.com> <30003DCB-33F1-4D8B-B141-AB1A175AFC82@mnot.net> <20130416074407.GA31249@nic.fr> <CAHBU6itK-FznB_OE5qzZJKM0QFPtbGdQZVQFb29fwrNpJfDq3w@mail.gmail.com>
To: Tim Bray <tbray@textuality.com>
X-Mailer: Apple Mail (2.1503)
Received-SPF: pass client-ip=216.86.168.182; envelope-from=mnot@mnot.net; helo=mxout-07.mxes.net
X-W3C-Hub-Spam-Status: No, score=-3.4
X-W3C-Hub-Spam-Report: AWL=-3.370, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001
X-W3C-Scan-Sig: maggie.w3.org 1USHlI-0001RC-Kk 73c05e260db3b9164a22ff9ec831a7ee
X-Original-To: ietf-http-wg@w3.org
Subject: Re: Status code 451 adoption
Archived-At: <http://www.w3.org/mid/15ACDF78-52A9-424F-B076-8CDB8B108EA4@mnot.net>
Resent-From: ietf-http-wg@w3.org
X-Mailing-List: <ietf-http-wg@w3.org> archive/latest/17277
X-Loop: ietf-http-wg@w3.org
Resent-Sender: ietf-http-wg-request@w3.org
Precedence: list
List-Id: <ietf-http-wg.w3.org>
List-Help: <http://www.w3.org/Mail/>
List-Post: <mailto:ietf-http-wg@w3.org>
List-Unsubscribe: <mailto:ietf-http-wg-request@w3.org?subject=unsubscribe>
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. Cheers, -- Mark Nottingham http://www.mnot.net/
- Status code 451 adoption Tim Bray
- Re: Status code 451 adoption Julian Reschke
- Re: Status code 451 adoption Mark Nottingham
- Re: Status code 451 adoption Stephane Bortzmeyer
- Re: Status code 451 adoption Mark Nottingham
- Re: Status code 451 adoption Tim Bray
- Re: Status code 451 adoption Tim Bray
- Re: Status code 451 adoption Julian Reschke