Re: HTTP status code for "response too large"

Jan Algermissen <jan.algermissen@nordsc.com> Wed, 18 April 2012 19:39 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 705EF21F854F for <ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com>; Wed, 18 Apr 2012 12:39:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.816
X-Spam-Level:
X-Spam-Status: No, score=-7.816 tagged_above=-999 required=5 tests=[AWL=2.783, 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 IZh4r8owtrk7 for <ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com>; Wed, 18 Apr 2012 12:39:54 -0700 (PDT)
Received: from frink.w3.org (frink.w3.org [128.30.52.56]) by ietfa.amsl.com (Postfix) with ESMTP id 8835A21F8532 for <httpbisa-archive-bis2Juki@lists.ietf.org>; Wed, 18 Apr 2012 12:39:54 -0700 (PDT)
Received: from lists by frink.w3.org with local (Exim 4.69) (envelope-from <ietf-http-wg-request@listhub.w3.org>) id 1SKaiW-0005AG-Uc for ietf-http-wg-dist@listhub.w3.org; Wed, 18 Apr 2012 19:39:04 +0000
Received: from lisa.w3.org ([128.30.52.41]) by frink.w3.org with esmtp (Exim 4.69) (envelope-from <jan.algermissen@nordsc.com>) id 1SKaiK-00059P-A9 for ietf-http-wg@listhub.w3.org; Wed, 18 Apr 2012 19:38:52 +0000
Received: from moutng.kundenserver.de ([212.227.17.8]) by lisa.w3.org with esmtp (Exim 4.72) (envelope-from <jan.algermissen@nordsc.com>) id 1SKaiE-0002US-7y for ietf-http-wg@w3.org; Wed, 18 Apr 2012 19:38:50 +0000
Received: from [192.168.2.103] (p548FA4F6.dip.t-dialin.net [84.143.164.246]) by mrelayeu.kundenserver.de (node=mreu3) with ESMTP (Nemesis) id 0MdArm-1Sbi980ZFK-00IEaA; Wed, 18 Apr 2012 21:38:04 +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: <OFD186EDCA.AF2D3EBA-ON852579E4.003EB3DE-852579E4.00403734@de.ibm.com>
Date: Wed, 18 Apr 2012 21:38:02 +0200
Cc: 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: <43384594-2129-400E-93E9-1000B5B525C8@nordsc.com>
References: <OFD186EDCA.AF2D3EBA-ON852579E4.003EB3DE-852579E4.00403734@de.ibm.com>
To: Andreas Maier <MAIERA@de.ibm.com>
X-Mailer: Apple Mail (2.1084)
X-Provags-ID: V02:K0:7uobCacOt5IRqQw+LB3bCzObLt74i6h2J+oRDawp9wH xIxEphJZAvcBGgqacIxJc7m2R55LDsmcK/K5F7ghrL+/8HyPi/ He/iPSSvuTYfzb875/lWfa+Uo7Gd7mpWBWVElP4O4rLdlPRWX9 TiVFFIm5cMGr9DcoRhwRrduAayhqrwrJSb4mSyncu1S6HLNr+e LbKb8TSo9dZyh8rjyhVp+5PRvICRPG411FS29PBGAesKQeFjqI vDJ9ZXuJxgCyK11FnOVXdardnWPl50scooPDAq1k9uR8JvinXT X4A1fSMjoTHhTrqkoJE4O9HFfekT6LY3p5rE4IvZH/n3BMpozT 7hjUk0/WgoSmAykf//rxD7XzyKxBK9OLN8+Byzps4DHdfSBnO6 JSR1WZW1Jj+2g==
Received-SPF: none client-ip=212.227.17.8; 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: lisa.w3.org 1SKaiE-0002US-7y 823e2d1029e607224dd825cab7cbf161
X-Original-To: ietf-http-wg@w3.org
Subject: Re: HTTP status code for "response too large"
Archived-At: <http://www.w3.org/mid/43384594-2129-400E-93E9-1000B5B525C8@nordsc.com>
Resent-From: ietf-http-wg@w3.org
X-Mailing-List: <ietf-http-wg@w3.org> archive/latest/13461
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: <E1SKaiW-0005AG-Uc@frink.w3.org>
Resent-Date: Wed, 18 Apr 2012 19:39:04 +0000

On Apr 18, 2012, at 1:41 PM, Andreas Maier wrote:

> 
> 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).
> 
> 

[snip]

>   - Do you have a recommendation on how to handle this situation?

Sounds like a response *entity* issue more than anything else. Use paging links[1] to allow the server to split the response as it sees fit.  

Jan

[1] http://www.ietf.org/rfc/rfc5005.txt