IETF Logo Mail Archive

Re: trailers and pseudo-headers

"Poul-Henning Kamp" <phk@phk.freebsd.dk> Wed, 02 July 2014 08:20 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 653B51B27C4 for <ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com>; Wed, 2 Jul 2014 01:20:25 -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 LGaPQ4mAvK58 for <ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com>; Wed, 2 Jul 2014 01:20:24 -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 73EB61B27B1 for <httpbisa-archive-bis2Juki@lists.ietf.org>; Wed, 2 Jul 2014 01:20:24 -0700 (PDT)
Received: from lists by frink.w3.org with local (Exim 4.72) (envelope-from <ietf-http-wg-request@listhub.w3.org>) id 1X2FkK-0003Ps-1f for ietf-http-wg-dist@listhub.w3.org; Wed, 02 Jul 2014 08:18:28 +0000
Resent-Date: Wed, 02 Jul 2014 08:18:28 +0000
Resent-Message-Id: <E1X2FkK-0003Ps-1f@frink.w3.org>
Received: from maggie.w3.org ([128.30.52.39]) by frink.w3.org with esmtp (Exim 4.72) (envelope-from <phk@phk.freebsd.dk>) id 1X2FkD-0003M3-Tb for ietf-http-wg@listhub.w3.org; Wed, 02 Jul 2014 08:18:21 +0000
Received: from phk.freebsd.dk ([130.225.244.222]) by maggie.w3.org with esmtp (Exim 4.72) (envelope-from <phk@phk.freebsd.dk>) id 1X2FkC-0007M3-Pq for ietf-http-wg@w3.org; Wed, 02 Jul 2014 08:18:21 +0000
Received: from critter.freebsd.dk (unknown [192.168.60.3]) by phk.freebsd.dk (Postfix) with ESMTP id 8A0EE16D0; Wed, 2 Jul 2014 08:17:59 +0000 (UTC)
Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.14.9/8.14.9) with ESMTP id s628HxSf020292; Wed, 2 Jul 2014 08:17:59 GMT (envelope-from phk@phk.freebsd.dk)
To: Julian Reschke <julian.reschke@gmx.de>
cc: Mark Nottingham <mnot@mnot.net>, HTTP Working Group <ietf-http-wg@w3.org>
In-reply-to: <53B3BF49.9030207@gmx.de>
From: Poul-Henning Kamp <phk@phk.freebsd.dk>
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> <53B3BF49.9030207@gmx.de>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <20290.1404289079.1@critter.freebsd.dk>
Date: Wed, 02 Jul 2014 08:17:59 +0000
Message-ID: <20291.1404289079@critter.freebsd.dk>
Received-SPF: none client-ip=130.225.244.222; envelope-from=phk@phk.freebsd.dk; helo=phk.freebsd.dk
X-W3C-Hub-Spam-Status: No, score=-3.4
X-W3C-Hub-Spam-Report: AWL=-3.419, T_RP_MATCHES_RCVD=-0.01
X-W3C-Scan-Sig: maggie.w3.org 1X2FkC-0007M3-Pq 767bd3c8933c390111a51f64950545c7
X-Original-To: ietf-http-wg@w3.org
Subject: Re: trailers and pseudo-headers
Archived-At: <http://www.w3.org/mid/20291.1404289079@critter.freebsd.dk>
Resent-From: ietf-http-wg@w3.org
X-Mailing-List: <ietf-http-wg@w3.org> archive/latest/25087
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>

In message <53B3BF49.9030207@gmx.de>, Julian Reschke writes:

>>> 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?

Exactly...  :status must be final and definitive before the client
can decide how to present or process the body.

-- 
Poul-Henning Kamp       | UNIX since Zilog Zeus 3.20
phk@FreeBSD.ORG         | TCP/IP since RFC 956
FreeBSD committer       | BSD since 4.3-tahoe    
Never attribute to malice what can adequately be explained by incompetence.

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