Re: #467: Expect: 100-continue and "final" status codes
Willy Tarreau <w@1wt.eu> Wed, 29 May 2013 05:17 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 C32C121F8FBE for <ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com>; Tue, 28 May 2013 22:17:42 -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 Jwr-gY7HM5Wz for <ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com>; Tue, 28 May 2013 22:17:36 -0700 (PDT)
Received: from frink.w3.org (frink.w3.org [128.30.52.56]) by ietfa.amsl.com (Postfix) with ESMTP id 8E5D321F8FBA for <httpbisa-archive-bis2Juki@lists.ietf.org>; Tue, 28 May 2013 22:17:36 -0700 (PDT)
Received: from lists by frink.w3.org with local (Exim 4.72) (envelope-from <ietf-http-wg-request@listhub.w3.org>) id 1UhYk0-00048K-OV for ietf-http-wg-dist@listhub.w3.org; Wed, 29 May 2013 05:16:04 +0000
Resent-Date: Wed, 29 May 2013 05:16:04 +0000
Resent-Message-Id: <E1UhYk0-00048K-OV@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 1UhYji-000470-CO for ietf-http-wg@listhub.w3.org; Wed, 29 May 2013 05:15:46 +0000
Received: from 1wt.eu ([62.212.114.60]) by maggie.w3.org with esmtp (Exim 4.72) (envelope-from <w@1wt.eu>) id 1UhYjh-0008Di-E1 for ietf-http-wg@w3.org; Wed, 29 May 2013 05:15:46 +0000
Received: (from willy@localhost) by mail.home.local (8.14.4/8.14.4/Submit) id r4T5FFL3006434; Wed, 29 May 2013 07:15:15 +0200
Date: Wed, 29 May 2013 07:15:15 +0200
From: Willy Tarreau <w@1wt.eu>
To: Michael Sweet <msweet@apple.com>
Cc: Zhong Yu <zhong.j.yu@gmail.com>, Mark Nottingham <mnot@mnot.net>, Ken Murchison <murch@andrew.cmu.edu>, HTTP Working Group <ietf-http-wg@w3.org>
Message-ID: <20130529051515.GA6426@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> <CACuKZqEfKFhCyDqeq_HpMfoG==jcx7xGifd=+qbUqErTZvBLjQ@mail.gmail.com> <A92880B4-EFDC-4695-B759-9A48959A2A67@apple.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <A92880B4-EFDC-4695-B759-9A48959A2A67@apple.com>
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 1UhYjh-0008Di-E1 db49ed2772d3612799f2ac83f5519fd2
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/20130529051515.GA6426@1wt.eu>
Resent-From: ietf-http-wg@w3.org
X-Mailing-List: <ietf-http-wg@w3.org> archive/latest/18140
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>
On Tue, May 28, 2013 at 12:04:16PM -0400, Michael Sweet wrote: > You'll still find many embedded HTTP servers that do not honor the Expect > header. CUPS has explicit timeout code on the client side for this since it > affects (far too) many IPP printers... :( Not to mention transparent 1.0 proxies which want to analyse the payload before passing the request. Regards, Willy
- p2: Expect: 100-continue and "final" status codes Mark Nottingham
- Re: p2: Expect: 100-continue and "final" status c… Zhong Yu
- Re: p2: Expect: 100-continue and "final" status c… Ken Murchison
- Re: p2: Expect: 100-continue and "final" status c… James M Snell
- Re: p2: Expect: 100-continue and "final" status c… Mark Nottingham
- Re: p2: Expect: 100-continue and "final" status c… Amos Jeffries
- Re: p2: Expect: 100-continue and "final" status c… Mark Nottingham
- Re: p2: Expect: 100-continue and "final" status c… Adrien W. de Croy
- Re: p2: Expect: 100-continue and "final" status c… Amos Jeffries
- Re: p2: Expect: 100-continue and "final" status c… Willy Tarreau
- Re: p2: Expect: 100-continue and "final" status c… Willy Tarreau
- Re: p2: Expect: 100-continue and "final" status c… Adrien W. de Croy
- Re: p2: Expect: 100-continue and "final" status c… Adrien W. de Croy
- Re: p2: Expect: 100-continue and "final" status c… Amos Jeffries
- Re: p2: Expect: 100-continue and "final" status c… Zhong Yu
- Re: p2: Expect: 100-continue and "final" status c… Ken Murchison
- Re: p2: Expect: 100-continue and "final" status c… Willy Tarreau
- Re: p2: Expect: 100-continue and "final" status c… Ken Murchison
- Re: p2: Expect: 100-continue and "final" status c… Willy Tarreau
- Re: p2: Expect: 100-continue and "final" status c… Daniel Stenberg
- Re: p2: Expect: 100-continue and "final" status c… Ken Murchison
- #467: Expect: 100-continue and "final" status cod… Mark Nottingham
- Re: #467: Expect: 100-continue and "final" status… Mark Nottingham
- Re: #467: Expect: 100-continue and "final" status… Willy Tarreau
- Re: #467: Expect: 100-continue and "final" status… Ken Murchison
- Re: #467: Expect: 100-continue and "final" status… Zhong Yu
- Re: #467: Expect: 100-continue and "final" status… Alex Rousskov
- Re: #467: Expect: 100-continue and "final" status… Mark Nottingham
- Re: #467: Expect: 100-continue and "final" status… Mark Nottingham
- Re: #467: Expect: 100-continue and "final" status… Willy Tarreau
- Re: #467: Expect: 100-continue and "final" status… Zhong Yu
- Re: #467: Expect: 100-continue and "final" status… Michael Sweet
- Re: Expect: 100-continue and "final" status codes Peter Occil
- Re: #467: Expect: 100-continue and "final" status… Willy Tarreau
- Re: #467: Expect: 100-continue and "final" status… Mark Nottingham