Re: Content-Range on responses other than 206

Yves Lafon <ylafon@w3.org> Tue, 26 July 2011 02: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 7C17311E80F2 for <ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com>; Mon, 25 Jul 2011 19:39:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.879
X-Spam-Level:
X-Spam-Status: No, score=-9.879 tagged_above=-999 required=5 tests=[AWL=0.120, BAYES_00=-2.599, J_CHICKENPOX_111=0.6, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id nc-7FgRQskx7 for <ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com>; Mon, 25 Jul 2011 19:39:56 -0700 (PDT)
Received: from frink.w3.org (frink.w3.org [128.30.52.56]) by ietfa.amsl.com (Postfix) with ESMTP id AEDDF11E80EB for <httpbisa-archive-bis2Juki@lists.ietf.org>; Mon, 25 Jul 2011 19:39:56 -0700 (PDT)
Received: from lists by frink.w3.org with local (Exim 4.69) (envelope-from <ietf-http-wg-request@listhub.w3.org>) id 1QlXXy-0005CU-VX for ietf-http-wg-dist@listhub.w3.org; Tue, 26 Jul 2011 02:39:02 +0000
Received: from maggie.w3.org ([128.30.52.39]) by frink.w3.org with esmtp (Exim 4.69) (envelope-from <ylafon@w3.org>) id 1QlXXn-0005Be-Fe for ietf-http-wg@listhub.w3.org; Tue, 26 Jul 2011 02:38:51 +0000
Received: from jay.w3.org ([128.30.52.169]) by maggie.w3.org with esmtp (Exim 4.72) (envelope-from <ylafon@w3.org>) id 1QlXXl-0004ki-Uc for ietf-http-wg@w3.org; Tue, 26 Jul 2011 02:38:51 +0000
Received: from ylafon by jay.w3.org with local (Exim 4.69) (envelope-from <ylafon@w3.org>) id 1QlXXl-0002Iy-Tx; Mon, 25 Jul 2011 22:38:49 -0400
Date: Mon, 25 Jul 2011 22:38:49 -0400
From: Yves Lafon <ylafon@w3.org>
To: Mark Nottingham <mnot@mnot.net>
cc: HTTP Working Group <ietf-http-wg@w3.org>
In-Reply-To: <FE504DA6-4D3A-4EAC-9416-4C28B832312A@mnot.net>
Message-ID: <alpine.DEB.1.10.1107252125180.27065@wnl.j3.bet>
References: <FE504DA6-4D3A-4EAC-9416-4C28B832312A@mnot.net>
User-Agent: Alpine 1.10 (DEB 962 2008-03-14)
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; format="flowed"; charset="ISO-8859-15"
Content-Transfer-Encoding: quoted-printable
X-W3C-Hub-Spam-Status: No, score=-4.1
X-W3C-Hub-Spam-Report: ALL_TRUSTED=-1, BAYES_00=-1.9, RP_MATCHES_RCVD=-1.191
X-W3C-Scan-Sig: maggie.w3.org 1QlXXl-0004ki-Uc 4e6a92bd8e74333fe62a867bf152d768
X-Original-To: ietf-http-wg@w3.org
Subject: Re: Content-Range on responses other than 206
Archived-At: <http://www.w3.org/mid/alpine.DEB.1.10.1107252125180.27065@wnl.j3.bet>
Resent-From: ietf-http-wg@w3.org
X-Mailing-List: <ietf-http-wg@w3.org> archive/latest/11089
X-Loop: ietf-http-wg@w3.org
Sender: ietf-http-wg-request@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: <E1QlXXy-0005CU-VX@frink.w3.org>
Resent-Date: Tue, 26 Jul 2011 02:39:02 +0000

On Fri, 15 Jul 2011, Mark Nottingham wrote:

> Anyone object to stating that Content-Range has no meaning on responses 
> that aren't 206's?
>
> Right now we don't say that, and it causes problems; see
>  http://gnats.netbsd.org/cgi-bin/query-pr-single.pl?number=45116

The issue here is the presense of a Content-Range header that identifies 
the whole representation, if the Content-Range header was identifying a 
sub-part it would be even more problematic, as the MUST-level requirement 
on C-R matching the payload bytes is in the definition of 206.

Proposal:
In Part5, section 5.2:

Old:
<<
The "Content-Range" header field is sent with a partial
representation to specify where in the full representation the
payload body is intended to be applied.
>>

New:
<<
The "Content-Range" header field is sent with a partial
representation to specify where in the full representation the
payload body is intended to be applied.

It MUST be ignored when present in responses with other response code than 
206 Partial Content [3.1].
>>


-- 
Baroula que barouleras, au tiƩu toujou t'entourneras.

         ~~Yves