HTTP status code for "response too large"
Andreas Maier <MAIERA@de.ibm.com> Wed, 18 April 2012 11:44 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 073C421F858B for <ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com>; Wed, 18 Apr 2012 04:44:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.11
X-Spam-Level:
X-Spam-Status: No, score=-9.11 tagged_above=-999 required=5 tests=[BAYES_05=-1.11, 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 WEbTgoXPjDjY for <ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com>; Wed, 18 Apr 2012 04:44:21 -0700 (PDT)
Received: from frink.w3.org (frink.w3.org [128.30.52.56]) by ietfa.amsl.com (Postfix) with ESMTP id 2C5AB21F8531 for <httpbisa-archive-bis2Juki@lists.ietf.org>; Wed, 18 Apr 2012 04:44:20 -0700 (PDT)
Received: from lists by frink.w3.org with local (Exim 4.69) (envelope-from <ietf-http-wg-request@listhub.w3.org>) id 1SKTHJ-0006ii-9L for ietf-http-wg-dist@listhub.w3.org; Wed, 18 Apr 2012 11:42:29 +0000
Received: from lisa.w3.org ([128.30.52.41]) by frink.w3.org with esmtp (Exim 4.69) (envelope-from <maiera@de.ibm.com>) id 1SKTH9-0006hm-AE for ietf-http-wg@listhub.w3.org; Wed, 18 Apr 2012 11:42:19 +0000
Received: from e06smtp16.uk.ibm.com ([195.75.94.112]) by lisa.w3.org with esmtp (Exim 4.72) (envelope-from <maiera@de.ibm.com>) id 1SKTGy-0006sf-Eg for ietf-http-wg@w3.org; Wed, 18 Apr 2012 11:42:17 +0000
Received: from /spool/local by e06smtp16.uk.ibm.com with IBM ESMTP SMTP Gateway: Authorized Use Only! Violators will be prosecuted for <ietf-http-wg@w3.org> from <maiera@de.ibm.com>; Wed, 18 Apr 2012 12:41:41 +0100
Received: from d06nrmr1507.portsmouth.uk.ibm.com (9.149.38.233) by e06smtp16.uk.ibm.com (192.168.101.146) with IBM ESMTP SMTP Gateway: Authorized Use Only! Violators will be prosecuted; Wed, 18 Apr 2012 12:41:39 +0100
Received: from d06av06.portsmouth.uk.ibm.com (d06av06.portsmouth.uk.ibm.com [9.149.37.217]) by d06nrmr1507.portsmouth.uk.ibm.com (8.13.8/8.13.8/NCO v10.0) with ESMTP id q3IBfcu71826976 for <ietf-http-wg@w3.org>; Wed, 18 Apr 2012 12:41:38 +0100
Received: from d06av06.portsmouth.uk.ibm.com (loopback [127.0.0.1]) by d06av06.portsmouth.uk.ibm.com (8.14.4/8.13.1/NCO v10.0 AVout) with ESMTP id q3IBfcW0032538 for <ietf-http-wg@w3.org>; Wed, 18 Apr 2012 05:41:38 -0600
Received: from d06ml032.portsmouth.uk.ibm.com (d06ml032.portsmouth.uk.ibm.com [9.149.76.137]) by d06av06.portsmouth.uk.ibm.com (8.14.4/8.13.1/NCO v10.0 AVin) with ESMTP id q3IBfcdP032533; Wed, 18 Apr 2012 05:41:38 -0600
X-KeepSent: D186EDCA:AF2D3EBA-852579E4:003EB3DE; type=4; name=$KeepSent
To: Mark Nottingham <mnot@pobox.com>
Cc: IETF HTTP WG <ietf-http-wg@w3.org>, Thomas Narten <tnarten@us.ibm.com>
X-Mailer: Lotus Notes Release 8.0.2 HF623 January 16, 2009
Message-ID: <OFD186EDCA.AF2D3EBA-ON852579E4.003EB3DE-852579E4.00403734@de.ibm.com>
From: Andreas Maier <MAIERA@de.ibm.com>
Date: Wed, 18 Apr 2012 07:41:24 -0400
X-MIMETrack: Serialize by Router on D06ML032/06/M/IBM(Release 8.5.2FP3|July 10, 2011) at 18/04/2012 13:41:32
MIME-Version: 1.0
Content-type: text/plain; charset="US-ASCII"
x-cbid: 12041811-3548-0000-0000-000001A731F3
Received-SPF: pass client-ip=195.75.94.112; envelope-from=maiera@de.ibm.com; helo=e06smtp16.uk.ibm.com
X-W3C-Hub-Spam-Status: No, score=-1.9
X-W3C-Hub-Spam-Report: BAYES_00=-1.9, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01
X-W3C-Scan-Sig: lisa.w3.org 1SKTGy-0006sf-Eg ee0795b5f28ba48eff87e7b1a54098b8
X-Original-To: ietf-http-wg@w3.org
Subject: HTTP status code for "response too large"
Archived-At: <http://www.w3.org/mid/OFD186EDCA.AF2D3EBA-ON852579E4.003EB3DE-852579E4.00403734@de.ibm.com>
Resent-From: ietf-http-wg@w3.org
X-Mailing-List: <ietf-http-wg@w3.org> archive/latest/13452
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: <E1SKTHJ-0006ii-9L@frink.w3.org>
Resent-Date: Wed, 18 Apr 2012 11:42:29 +0000
Hi Mark, I am working for IBM in the DMTF standards org. We are defining a RESTful protocol for CIM based directly on HTTP ("CIM-RS"), and we want to be as truthfully RESTful and HTTP compliant as possible. We want to support an "expand" query parameter that causes references to resources in the result to be expanded to the resources that they reference. One of the error situations in this context is that the expansion can lead to a result that is too large to handle for the server (e.g. in cases of high mutiplicities on CIM associations). The recovery for this situation is that the client specifies less expansions in the first request issues subsequent requests for separate expansion (one per reference, which can then be paged into multiple responses in case of high multiplicities). So it is not the typical server-side recovery, where the client waits for less load on the server or the server admin needs to add more resources to the server. The recovery attempt can be immediately decided upon by the client without any change in server configuration or workload. We'd like to have a HTTP status code that allows the client to detect this situation so it can recover from it. In order to make it easy for the client, I think that should not be a use of status code 500, but its own status code. I checked all status codes on the IANA HTTP status code registry and found no one that matched this situation. But I found that the HTTP WG is working on an RFC for additional HTTP status codes that is currently in draft :-) So my questions to you and the WG are: - Do you have a recommendation on how to handle this situation? - How is your view on the idea to add an HTTP status code for "response too large"? PS: If you're interested in CIM-RS, what you find currently on the DMTF site or when googling it are informational specs from an incubator that do not yet have the "expand" query parameter. The real specs from the CIM-RS WG are about to be released as a Work in Progress in the next weeks. Andy Andreas Maier IBM Senior Technical Staff Member, Systems Management Architecture & Design IBM Research & Development Laboratory Boeblingen, Germany maiera@de.ibm.com, +49-7031-16-3654 ________________________________________________________________________ IBM Deutschland Research & Development GmbH Vorsitzende des Aufsichtsrats: Martina Koederitz Geschaeftsfuehrung: Dirk Wittkopp Sitz der Gesellschaft: Boeblingen Registergericht: Amtsgericht Stuttgart, HRB 243294
- 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