Re: trailers and pseudo-headers

Mark Nottingham <mnot@mnot.net> Wed, 02 July 2014 06:52 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 34D1D1B28DB for <ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com>; Tue, 1 Jul 2014 23:52:14 -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 MCY5fU5oEUPu for <ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com>; Tue, 1 Jul 2014 23:52:12 -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 B22D41B28DA for <httpbisa-archive-bis2Juki@lists.ietf.org>; Tue, 1 Jul 2014 23:52:12 -0700 (PDT)
Received: from lists by frink.w3.org with local (Exim 4.72) (envelope-from <ietf-http-wg-request@listhub.w3.org>) id 1X2EMY-0007e6-Oq for ietf-http-wg-dist@listhub.w3.org; Wed, 02 Jul 2014 06:49:50 +0000
Resent-Date: Wed, 02 Jul 2014 06:49:50 +0000
Resent-Message-Id: <E1X2EMY-0007e6-Oq@frink.w3.org>
Received: from maggie.w3.org ([128.30.52.39]) by frink.w3.org with esmtp (Exim 4.72) (envelope-from <mnot@mnot.net>) id 1X2EMV-0007cj-OR for ietf-http-wg@listhub.w3.org; Wed, 02 Jul 2014 06:49:47 +0000
Received: from mxout-07.mxes.net ([216.86.168.182]) by maggie.w3.org with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.72) (envelope-from <mnot@mnot.net>) id 1X2EMU-0003xl-Te for ietf-http-wg@w3.org; Wed, 02 Jul 2014 06:49:47 +0000
Received: from [192.168.1.55] (unknown [118.209.193.75]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by smtp.mxes.net (Postfix) with ESMTPSA id 27A3322E1F3; Wed, 2 Jul 2014 02:49:23 -0400 (EDT)
Content-Type: text/plain; charset="iso-8859-1"
Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.2\))
From: Mark Nottingham <mnot@mnot.net>
In-Reply-To: <53B3A631.80907@gmx.de>
Date: Wed, 02 Jul 2014 16:49:20 +1000
Cc: HTTP Working Group <ietf-http-wg@w3.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <0A3A3665-FEBD-467D-857A-6D1E61C83056@mnot.net>
References: <53B3A631.80907@gmx.de>
To: "Julian F. Reschke" <julian.reschke@gmx.de>
X-Mailer: Apple Mail (2.1878.2)
Received-SPF: pass client-ip=216.86.168.182; envelope-from=mnot@mnot.net; helo=mxout-07.mxes.net
X-W3C-Hub-Spam-Status: No, score=-3.7
X-W3C-Hub-Spam-Report: AWL=-3.018, RCVD_IN_DNSWL_LOW=-0.7, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001
X-W3C-Scan-Sig: maggie.w3.org 1X2EMU-0003xl-Te 989ec5424d740212e13696b65556b15c
X-Original-To: ietf-http-wg@w3.org
Subject: Re: trailers and pseudo-headers
Archived-At: <http://www.w3.org/mid/0A3A3665-FEBD-467D-857A-6D1E61C83056@mnot.net>
Resent-From: ietf-http-wg@w3.org
X-Mailing-List: <ietf-http-wg@w3.org> archive/latest/25062
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 2 Jul 2014, at 4:26 pm, Julian Reschke <julian.reschke@gmx.de> wrote:

> Hi there,
> 
> should we say something about the case where a HEADERS frame containing trailing header fields contains pseudo-headers such as ":status"?
> 
> Allowed? Forbidden? Bad idea?

My .02 - probably, although <http://httpwg.github.io/specs/rfc7230.html#chunked.trailer.part> says:

> A sender must not generate a trailer that contains a field necessary for message framing (e.g., Transfer-Encoding and Content-Length), routing (e.g., Host), request modifiers (e.g., controls and conditionals in Section 5 of [RFC7231]), authentication (e.g., see [RFC7235]and [RFC6265]), response control data (e.g., see Section 7.1 of [RFC7231]), or determining how to process the payload (e.g., Content-Encoding, Content-Type, Content-Range, and Trailer).

... which kind of already goes there. Maybe just note that they fall under that requirement?

--
Mark Nottingham   https://www.mnot.net/