Re: HTTP status code for "response too large"
Jan Algermissen <jan.algermissen@nordsc.com> Wed, 18 April 2012 17:43 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 D101421F84CD for <ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com>; Wed, 18 Apr 2012 10:43:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.424
X-Spam-Level:
X-Spam-Status: No, score=-6.424 tagged_above=-999 required=5 tests=[AWL=4.175, 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 ekZ39b9ZI9m4 for <ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com>; Wed, 18 Apr 2012 10:43:22 -0700 (PDT)
Received: from frink.w3.org (frink.w3.org [128.30.52.56]) by ietfa.amsl.com (Postfix) with ESMTP id D2B2F21F84C9 for <httpbisa-archive-bis2Juki@lists.ietf.org>; Wed, 18 Apr 2012 10:43:22 -0700 (PDT)
Received: from lists by frink.w3.org with local (Exim 4.69) (envelope-from <ietf-http-wg-request@listhub.w3.org>) id 1SKYtD-0007vZ-D0 for ietf-http-wg-dist@listhub.w3.org; Wed, 18 Apr 2012 17:41:59 +0000
Received: from maggie.w3.org ([128.30.52.39]) by frink.w3.org with esmtp (Exim 4.69) (envelope-from <jan.algermissen@nordsc.com>) id 1SKYsm-0007gv-2J for ietf-http-wg@listhub.w3.org; Wed, 18 Apr 2012 17:41:32 +0000
Received: from moutng.kundenserver.de ([212.227.126.171]) by maggie.w3.org with esmtp (Exim 4.72) (envelope-from <jan.algermissen@nordsc.com>) id 1SKYsf-0007RF-TR for ietf-http-wg@w3.org; Wed, 18 Apr 2012 17:41:30 +0000
Received: from [192.168.2.103] (p548FA4F6.dip.t-dialin.net [84.143.164.246]) by mrelayeu.kundenserver.de (node=mrbap0) with ESMTP (Nemesis) id 0M835V-1S7PlV0r8D-00vhGd; Wed, 18 Apr 2012 19:40:44 +0200
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset="us-ascii"
From: Jan Algermissen <jan.algermissen@nordsc.com>
In-Reply-To: <2033EB77-610A-447F-BEE6-C0B9CF53A2CF@mnot.net>
Date: Wed, 18 Apr 2012 19:40:43 +0200
Cc: Cyrus Daboo <cyrus@daboo.name>, Julian Reschke <julian.reschke@gmx.de>, Andreas Maier <MAIERA@de.ibm.com>, Mark Nottingham <mnot@pobox.com>, IETF HTTP WG <ietf-http-wg@w3.org>, Thomas Narten <tnarten@us.ibm.com>
Content-Transfer-Encoding: quoted-printable
Message-Id: <1478AE47-8CF8-4815-A605-233EBD0F938A@nordsc.com>
References: <OFD186EDCA.AF2D3EBA-ON852579E4.003EB3DE-852579E4.00403734@de.ibm.com> <4F8EAC1A.5000707@gmx.de> <214DE30B03E5CC7C7FE4CF6C@caldav.corp.apple.com> <4F8ED467.6020809@gmx.de> <25172B451C65D28F02CDAB63@caldav.corp.apple.com> <2033EB77-610A-447F-BEE6-C0B9CF53A2CF@mnot.net>
To: Mark Nottingham <mnot@mnot.net>
X-Mailer: Apple Mail (2.1084)
X-Provags-ID: V02:K0:rbhw8UJ3q7d1zopLHB2hWtQ9t9a92Inik5A/xbD19TF s3jMbY00t1+wurHRRDHKYqx0smSH1wrKYop3ZcH849tNCMJ3yb rev+DLh3n+Xbdfo7R3AZSSC6g6Q9D03rXvHx/FfXVnM78Ct5pV cprVtAvJMMLwY53F08/YO1rZ+WDT/4nFcjqo/GdDaaHgaGogEO qTIkRRXKLp9XltCNYHxAz7LIpGqLqbj3LmafKsw1llNK7WHkbm V4xMjaZj0T28jUyddeVPnQO+ku2UzcX3dmGHjku2teUhzosGgC WeSg2du3iAMN6ZA2gYCVa2+zFusAkft1LlkCKs31Fb5JT9rUmW R0kRddL7UNJ+jWDbvwcyZnJ8lmzFEFgUhdCgAzSBG+tOcUSsZV J7OQT+YeUDVMA==
Received-SPF: none client-ip=212.227.126.171; envelope-from=jan.algermissen@nordsc.com; helo=moutng.kundenserver.de
X-W3C-Hub-Spam-Status: No, score=-1.9
X-W3C-Hub-Spam-Report: BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_PASS=-0.001
X-W3C-Scan-Sig: maggie.w3.org 1SKYsf-0007RF-TR d6c10f64b9dc124ad752295aac24c38c
X-Original-To: ietf-http-wg@w3.org
Subject: Re: HTTP status code for "response too large"
Archived-At: <http://www.w3.org/mid/1478AE47-8CF8-4815-A605-233EBD0F938A@nordsc.com>
Resent-From: ietf-http-wg@w3.org
X-Mailing-List: <ietf-http-wg@w3.org> archive/latest/13459
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>
Resent-Message-Id: <E1SKYtD-0007vZ-D0@frink.w3.org>
Resent-Date: Wed, 18 Apr 2012 17:41:59 +0000
On Apr 18, 2012, at 5:32 PM, Mark Nottingham wrote: > > This is a good illustration of How Not To Do It. 507 should have been more generic, focusing on the interface rather than the implementation (as Roy constantly reminds us). > FWIW, I read about 507 the first time just now and I would never have thought it applies to the response. IMHO, the definition seems to actually work quite well. Jan > > Cheers, > > -- > Mark Nottingham > http://www.mnot.net/ > > > > >
- Re: HTTP status code for "response too large" Julian Reschke
- HTTP status code for "response too large" Andreas Maier
- Re: HTTP status code for "response too large" Cyrus Daboo
- Re: HTTP status code for "response too large" Julian Reschke
- Re: HTTP status code for "response too large" Cyrus Daboo
- Re: HTTP status code for "response too large" Mark Nottingham
- Re: HTTP status code for "response too large" Julian Reschke
- Re: HTTP status code for "response too large" Jan Algermissen
- Re: HTTP status code for "response too large" Jan Algermissen