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

Mark Nottingham <mnot@mnot.net> Fri, 17 May 2013 02:49 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 []) by ietfa.amsl.com (Postfix) with ESMTP id 7ADBF11E80A3 for <ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com>; Thu, 16 May 2013 19:49:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.124
X-Spam-Status: No, score=-7.124 tagged_above=-999 required=5 tests=[AWL=3.475, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([]) by localhost (ietfa.amsl.com []) (amavisd-new, port 10024) with ESMTP id h8X5lh4GWJ5h for <ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com>; Thu, 16 May 2013 19:49:38 -0700 (PDT)
Received: from frink.w3.org (frink.w3.org []) by ietfa.amsl.com (Postfix) with ESMTP id 3EFA111E80ED for <httpbisa-archive-bis2Juki@lists.ietf.org>; Thu, 16 May 2013 19:49:37 -0700 (PDT)
Received: from lists by frink.w3.org with local (Exim 4.72) (envelope-from <ietf-http-wg-request@listhub.w3.org>) id 1UdAiK-00054b-Fs for ietf-http-wg-dist@listhub.w3.org; Fri, 17 May 2013 02:48:12 +0000
Resent-Date: Fri, 17 May 2013 02:48:12 +0000
Resent-Message-Id: <E1UdAiK-00054b-Fs@frink.w3.org>
Received: from lisa.w3.org ([]) by frink.w3.org with esmtp (Exim 4.72) (envelope-from <mnot@mnot.net>) id 1UdAi9-00053L-Bw for ietf-http-wg@listhub.w3.org; Fri, 17 May 2013 02:48:01 +0000
Received: from mxout-07.mxes.net ([]) by lisa.w3.org with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.72) (envelope-from <mnot@mnot.net>) id 1UdAi3-0000m0-Uu for ietf-http-wg@w3.org; Fri, 17 May 2013 02:48:00 +0000
Received: from [] (unknown []) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by smtp.mxes.net (Postfix) with ESMTPSA id 804B322E1FA; Thu, 16 May 2013 22:47:32 -0400 (EDT)
Content-Type: text/plain; charset=windows-1252
Mime-Version: 1.0 (Mac OS X Mail 6.3 \(1503\))
From: Mark Nottingham <mnot@mnot.net>
In-Reply-To: <20130424170638.GD19750@1wt.eu>
Date: Fri, 17 May 2013 12:47:27 +1000
Cc: Ken Murchison <murch@andrew.cmu.edu>, ietf-http-wg@w3.org
Content-Transfer-Encoding: quoted-printable
Message-Id: <1CD0C86A-CFBF-4DF6-A688-9E4EF549190E@mnot.net>
References: <CACuKZqGmrDiNQvG0SVw=XXcy_n-BBxK-pnp+ar7uAbnwkumRag@mail.gmail.com> <51780FBA.3080706@andrew.cmu.edu> <20130424170638.GD19750@1wt.eu>
To: Willy Tarreau <w@1wt.eu>
X-Mailer: Apple Mail (2.1503)
Received-SPF: pass client-ip=; envelope-from=mnot@mnot.net; helo=mxout-07.mxes.net
X-W3C-Hub-Spam-Status: No, score=-3.4
X-W3C-Hub-Spam-Report: AWL=-3.388, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001
X-W3C-Scan-Sig: lisa.w3.org 1UdAi3-0000m0-Uu 26e870143466bb7893aa7d1ed4d6dd70
X-Original-To: ietf-http-wg@w3.org
Subject: #467: Expect: 100-continue and "final" status codes
Archived-At: <http://www.w3.org/mid/1CD0C86A-CFBF-4DF6-A688-9E4EF549190E@mnot.net>
Resent-From: ietf-http-wg@w3.org
X-Mailing-List: <ietf-http-wg@w3.org> archive/latest/18016
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>

Looking at this again, I think one of the problems is that people misunderstand what e/c is for.

The current definition of 100-continue in requests doesn't help:

> 100-continue
> 	• The request includes a payload body and the client will wait for a 100 (Continue) response after sending the request header section but before sending the payload body. The 100-continue expectation does not use any expect-params.


"will wait for" is misleading here; the client might send the body before getting the 100 response. This should really say something like:


* The request includes a payload body and, after sending the request header section, the client will wait before some 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.

It then goes on:

> The primary purpose of the 100 (Continue) status code (Section 6.2.1) is to allow a client that is sending a request message with a payload to determine if the origin server is willing to accept the request (based on the request header fields) before the client sends the payload body. In some cases, it might either be inappropriate or highly inefficient for the client to send the payload body if the server will reject the message without looking at the body.

Again, I think this is misleading. It should say something like:

The 100-continue expectation and 100 (Continue) status code (Section 6.2.1) are useful when a request that has a large body might be rejected by the server; for example, if the request requires authorization (ref to p7). In these situations, clients will often pause between sending the request headers and its body, to give the server an opportunity to refuse the request. 

In cases where the request is successful, this can cause a needless delay, as the client waits to time out (a typical period is one second). If the client has send the 100-continue expectation, the server can use the 100 (Continue) status code to indicate that the request is not going to be rejected, thereby avoiding the remainder of this delay period.

Note that this mechanism does not change the request message parsing algorithm; in particular, whether or not a final response status code is sent, the client still needs to send a complete request message. As such, if a final status code is received, clients will often choose to close the connection, rather than send a complete request (e.g., if it is length-delimited).

If we can agree on that, I think it'll help guide the rest of the discussion here and in the other E/C related issues:

Am I on track?


On 25/04/2013, at 3:06 AM, Willy Tarreau <w@1wt.eu> wrote:

> On Wed, Apr 24, 2013 at 01:00:42PM -0400, Ken Murchison wrote:
>>> 2. If the client receives a final status code instead of 100 
>>> (Continue), it
>>> should stop sending request body if it is doing so; it must close the
>>> connection after the response is received.
>> I don't understand point #2.  If the client submits a request with 
>> Expect:100-continue, I would assume that the client MUST NOT send any 
>> part of the body until it receives 100 (Continue) from the server.  If 
>> the server rejects the request based on the headers (with 412, 415, 417, 
>> etc) there should be no body data in the pipe for either the client or 
>> server to worry about, correct?
> In fact the client can decide that it's been waiting too long for 100
> and decides to send anyway (because some old servers or intermediaries
> do not know about Expect and will wait).
> So what is generally done is that the client sends the headers, waits a
> bit then starts to send data if the server does not respond.
> Implementation of expect+100 seems to be a real mess at some places,
> but when it works it prove to be quite useful.
> Willy

Mark Nottingham   http://www.mnot.net/