Re: #467: Expect: 100-continue and "final" status codes

Willy Tarreau <w@1wt.eu> Tue, 28 May 2013 06:24 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 5AC7021F93F1 for <ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com>; Mon, 27 May 2013 23:24:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.599
X-Spam-Level:
X-Spam-Status: No, score=-10.599 tagged_above=-999 required=5 tests=[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 FiqPPmIZIxti for <ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com>; Mon, 27 May 2013 23:24:13 -0700 (PDT)
Received: from frink.w3.org (frink.w3.org [128.30.52.56]) by ietfa.amsl.com (Postfix) with ESMTP id 97BFE21F8EA4 for <httpbisa-archive-bis2Juki@lists.ietf.org>; Mon, 27 May 2013 23:24:13 -0700 (PDT)
Received: from lists by frink.w3.org with local (Exim 4.72) (envelope-from <ietf-http-wg-request@listhub.w3.org>) id 1UhDJq-0000LN-Nl for ietf-http-wg-dist@listhub.w3.org; Tue, 28 May 2013 06:23:38 +0000
Resent-Date: Tue, 28 May 2013 06:23:38 +0000
Resent-Message-Id: <E1UhDJq-0000LN-Nl@frink.w3.org>
Received: from maggie.w3.org ([128.30.52.39]) by frink.w3.org with esmtp (Exim 4.72) (envelope-from <w@1wt.eu>) id 1UhDJe-0000K6-LC for ietf-http-wg@listhub.w3.org; Tue, 28 May 2013 06:23:26 +0000
Received: from 1wt.eu ([62.212.114.60]) by maggie.w3.org with esmtp (Exim 4.72) (envelope-from <w@1wt.eu>) id 1UhDJZ-0001TT-KP for ietf-http-wg@w3.org; Tue, 28 May 2013 06:23:26 +0000
Received: (from willy@localhost) by mail.home.local (8.14.4/8.14.4/Submit) id r4S6MqqX030736; Tue, 28 May 2013 08:22:52 +0200
Date: Tue, 28 May 2013 08:22:52 +0200
From: Willy Tarreau <w@1wt.eu>
To: Mark Nottingham <mnot@mnot.net>
Cc: Zhong Yu <zhong.j.yu@gmail.com>, Ken Murchison <murch@andrew.cmu.edu>, HTTP Working Group <ietf-http-wg@w3.org>
Message-ID: <20130528062252.GA30665@1wt.eu>
References: <CACuKZqGmrDiNQvG0SVw=XXcy_n-BBxK-pnp+ar7uAbnwkumRag@mail.gmail.com> <51780FBA.3080706@andrew.cmu.edu> <20130424170638.GD19750@1wt.eu> <1CD0C86A-CFBF-4DF6-A688-9E4EF549190E@mnot.net> <CACuKZqGwm+aH+jRSNmKsfdDwe3eCVhmtr=u0rbUFC2+G99T5VQ@mail.gmail.com> <9C460363-84A8-459E-A9F1-B6A1219F31D7@mnot.net>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <9C460363-84A8-459E-A9F1-B6A1219F31D7@mnot.net>
User-Agent: Mutt/1.4.2.3i
Received-SPF: pass client-ip=62.212.114.60; envelope-from=w@1wt.eu; helo=1wt.eu
X-W3C-Hub-Spam-Status: No, score=-3.6
X-W3C-Hub-Spam-Report: AWL=-2.525, RP_MATCHES_RCVD=-1.07, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001
X-W3C-Scan-Sig: maggie.w3.org 1UhDJZ-0001TT-KP ad6e0da4ead8edef8c80e05ba187d066
X-Original-To: ietf-http-wg@w3.org
Subject: Re: #467: Expect: 100-continue and "final" status codes
Archived-At: <http://www.w3.org/mid/20130528062252.GA30665@1wt.eu>
Resent-From: ietf-http-wg@w3.org
X-Mailing-List: <ietf-http-wg@w3.org> archive/latest/18107
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>

Hi Mark,

On Tue, May 28, 2013 at 04:03:36PM +1000, Mark Nottingham wrote:
> There aren't any new requirements in there; all of this text is only
> describing semantics and giving implementation advice. What if we modify the
> text slightly, e.g.,
> 
> """
> 100-continue
> 
> * The request includes a payload body and, after sending the request header
> section, the client will wait before some (possibly unbounded) period of time
> before sending it, to give the server an opportunity to reject the request
> with a final status code. The server can shorten the wait time by sending a
> 100 (Continue) response.
> """

I personally think the "possibly unbounded" part solves the issue. However,
we should ass "or a final status code" at the end of the last sentence.

Best regards,
Willy