IETF Logo Mail Archive

Re: trailers and pseudo-headers

Julian Reschke <julian.reschke@gmx.de> Wed, 02 July 2014 08: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 (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0F6841B28E0 for <ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com>; Wed, 2 Jul 2014 01:17:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.553
X-Spam-Level:
X-Spam-Status: No, score=-7.553 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.651, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id c5iJDEsCmP03 for <ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com>; Wed, 2 Jul 2014 01:16:58 -0700 (PDT)
Received: from frink.w3.org (frink.w3.org [128.30.52.56]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 112E71B27B1 for <httpbisa-archive-bis2Juki@lists.ietf.org>; Wed, 2 Jul 2014 01:16:57 -0700 (PDT)
Received: from lists by frink.w3.org with local (Exim 4.72) (envelope-from <ietf-http-wg-request@listhub.w3.org>) id 1X2Fgk-00080I-BF for ietf-http-wg-dist@listhub.w3.org; Wed, 02 Jul 2014 08:14:46 +0000
Resent-Date: Wed, 02 Jul 2014 08:14:46 +0000
Resent-Message-Id: <E1X2Fgk-00080I-BF@frink.w3.org>
Received: from maggie.w3.org ([128.30.52.39]) by frink.w3.org with esmtp (Exim 4.72) (envelope-from <julian.reschke@gmx.de>) id 1X2Fgf-0007yV-42 for ietf-http-wg@listhub.w3.org; Wed, 02 Jul 2014 08:14:41 +0000
Received: from mout.gmx.net ([212.227.17.20]) by maggie.w3.org with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.72) (envelope-from <julian.reschke@gmx.de>) id 1X2FgZ-0007Af-3q for ietf-http-wg@w3.org; Wed, 02 Jul 2014 08:14:41 +0000
Received: from [192.168.2.160] ([93.217.120.194]) by mail.gmx.com (mrgmx103) with ESMTPSA (Nemesis) id 0LmrZY-1WRmrk07dE-00h33N; Wed, 02 Jul 2014 10:14:08 +0200
Message-ID: <53B3BF49.9030207@gmx.de>
Date: Wed, 02 Jul 2014 10:14:01 +0200
From: Julian Reschke <julian.reschke@gmx.de>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.6.0
MIME-Version: 1.0
To: Poul-Henning Kamp <phk@phk.freebsd.dk>
CC: Mark Nottingham <mnot@mnot.net>, HTTP Working Group <ietf-http-wg@w3.org>
References: <53B3A631.80907@gmx.de> <0A3A3665-FEBD-467D-857A-6D1E61C83056@mnot.net> <53B3AD3A.8020307@gmx.de> <19984.1404286540@critter.freebsd.dk> <53B3B835.80807@gmx.de> <20154.1404288175@critter.freebsd.dk>
In-Reply-To: <20154.1404288175@critter.freebsd.dk>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
X-Provags-ID: V03:K0:lMvSIJ2llBZUXs/UtDLmJdByXsgGVc2sgT4YYlDTH3lvMgl0aFM FBLztzhBGZDiBJ1gpjbcFXHb+dVdCpMNT28dRBEKSdpFbJ9kXLaSf/Cndoahz2+0uQdz3gS qikmF/s53qg+DgpvHeI0H1G1q6C93SNRNMm5V6yKANttSlcXUjPewWQdxuiJ/jn5nnQHJAP LFUZ4JVLsoNiM/eQW3igw==
Received-SPF: pass client-ip=212.227.17.20; envelope-from=julian.reschke@gmx.de; helo=mout.gmx.net
X-W3C-Hub-Spam-Status: No, score=-3.4
X-W3C-Hub-Spam-Report: AWL=-3.429, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001
X-W3C-Scan-Sig: maggie.w3.org 1X2FgZ-0007Af-3q 8d542eb3e91546757fd5e5c203526172
X-Original-To: ietf-http-wg@w3.org
Subject: Re: trailers and pseudo-headers
Archived-At: <http://www.w3.org/mid/53B3BF49.9030207@gmx.de>
Resent-From: ietf-http-wg@w3.org
X-Mailing-List: <ietf-http-wg@w3.org> archive/latest/25086
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 2014-07-02 10:02, Poul-Henning Kamp wrote:
> In message <53B3B835.80807@gmx.de>, Julian Reschke writes:
>> On 2014-07-02 09:35, Poul-Henning Kamp wrote:
>>> In message <53B3AD3A.8020307@gmx.de>, Julian Reschke writes:
>>>
>>>> The reason I ask is that people might start putting ":status" into a
>>>> trailer and expect that to have an effect (it would be nice to have that
>>>> feature, but it wouldn't map to 1.1...).
>>>
>>> It would also be pretty pointless:  It would just shift the buffering
>>> responsibility from the server to the client.
>>
>> What I meant is: an *additional* :status (such as in first claiming
>> everything is ok -- 200, then start streaming and failing, and then send
>> a 500 in the trailers).
>
> And if that is a risk, the client can do only one thing:  Buffer the
> response, until it is sure what the :status will be.

Hm? That would imply buffering all responses before displaying them?

v2.28.0 | Report a Bug | By Email | System Status