Re: p2: Expect: 100-continue and "final" status codes

"Adrien W. de Croy" <adrien@qbik.com> Wed, 24 April 2013 08:36 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 027FF21F8F1F for <ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com>; Wed, 24 Apr 2013 01:36:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.266
X-Spam-Level:
X-Spam-Status: No, score=-9.266 tagged_above=-999 required=5 tests=[AWL=1.333, 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 uHuWcEsFc5Ln for <ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com>; Wed, 24 Apr 2013 01:36:18 -0700 (PDT)
Received: from frink.w3.org (frink.w3.org [128.30.52.56]) by ietfa.amsl.com (Postfix) with ESMTP id 78D9121F8AE8 for <httpbisa-archive-bis2Juki@lists.ietf.org>; Wed, 24 Apr 2013 01:36:18 -0700 (PDT)
Received: from lists by frink.w3.org with local (Exim 4.72) (envelope-from <ietf-http-wg-request@listhub.w3.org>) id 1UUvAH-0007A5-89 for ietf-http-wg-dist@listhub.w3.org; Wed, 24 Apr 2013 08:34:57 +0000
Resent-Date: Wed, 24 Apr 2013 08:34:57 +0000
Resent-Message-Id: <E1UUvAH-0007A5-89@frink.w3.org>
Received: from lisa.w3.org ([128.30.52.41]) by frink.w3.org with esmtp (Exim 4.72) (envelope-from <adrien@qbik.com>) id 1UUvAD-00079M-I8 for ietf-http-wg@listhub.w3.org; Wed, 24 Apr 2013 08:34:53 +0000
Received: from smtp.qbik.com ([210.55.214.35]) by lisa.w3.org with esmtp (Exim 4.72) (envelope-from <adrien@qbik.com>) id 1UUvAC-00023t-Id for ietf-http-wg@w3.org; Wed, 24 Apr 2013 08:34:53 +0000
Received: From [192.168.0.10] (unverified [192.168.0.10]) by SMTP Server [192.168.0.1] (WinGate SMTP Receiver v8.0.0 (Build 4540)) with SMTP id <0019670540@smtp.qbik.com>; Wed, 24 Apr 2013 20:34:30 +1200
From: "Adrien W. de Croy" <adrien@qbik.com>
To: "Amos Jeffries" <squid3@treenet.co.nz>, "ietf-http-wg@w3.org" <ietf-http-wg@w3.org>
Date: Wed, 24 Apr 2013 08:34:30 +0000
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain; format=flowed; charset=utf-8
In-Reply-To: <51774650.50104@treenet.co.nz>
Message-Id: <em9da5a567-6b0f-4b8c-b113-080fb794c5e2@bombed>
Mime-Version: 1.0
Reply-To: "Adrien W. de Croy" <adrien@qbik.com>
User-Agent: eM_Client/5.0.17595.0
Received-SPF: pass client-ip=210.55.214.35; envelope-from=adrien@qbik.com; helo=smtp.qbik.com
X-W3C-Hub-Spam-Status: No, score=-3.4
X-W3C-Hub-Spam-Report: AWL=-3.392, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001
X-W3C-Scan-Sig: lisa.w3.org 1UUvAC-00023t-Id d0887086fa379b2f118d995735b4f778
X-Original-To: ietf-http-wg@w3.org
Subject: Re: p2: Expect: 100-continue and "final" status codes
Archived-At: <http://www.w3.org/mid/em9da5a567-6b0f-4b8c-b113-080fb794c5e2@bombed>
Resent-From: ietf-http-wg@w3.org
X-Mailing-List: <ietf-http-wg@w3.org> archive/latest/17533
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>

------ Original Message ------
From: "Amos Jeffries" <squid3@treenet.co.nz>;

>The problem comes with intermediaries. How are they to know the bytes 
>following were the original advertised payload or not? the status from 
>server has no guarantee of arriving after the client payload starts 
>arriving.

Any bytes after the request + headers but not including advertised 
payload must be payload.  There's no other option apart from closing 
(e.g. another request is not an option, since the first message has not 
been sent until any advertised payload is sent, or if it's chunked a 0 
chunk has been sent).

So there's no ambiguity and no need for an intermediary to have 
previously received the server response (initial or otherwise).

Adrien

>The only way to guarantee safety on the connection is to close it or 
>always send payload.
>
>Amos
>