Re: What we call "headers"
Poul-Henning Kamp <phk@phk.freebsd.dk> Thu, 19 March 2020 16:48 UTC
Return-Path: <ietf-http-wg-request+bounce-httpbisa-archive-bis2juki=lists.ie@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 3F2E93A0993 for <ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com>; Thu, 19 Mar 2020 09:48:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.641
X-Spam-Level:
X-Spam-Status: No, score=-2.641 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.249, MAILING_LIST_MULTI=-1, SPF_PASS=-0.001, T_SPF_HELO_TEMPERROR=0.01, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
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 OCPQkzBm5ohZ for <ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com>; Thu, 19 Mar 2020 09:48:02 -0700 (PDT)
Received: from lyra.w3.org (lyra.w3.org [128.30.52.18]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id DAB443A0966 for <httpbisa-archive-bis2Juki@lists.ietf.org>; Thu, 19 Mar 2020 09:48:01 -0700 (PDT)
Received: from lists by lyra.w3.org with local (Exim 4.92) (envelope-from <ietf-http-wg-request@listhub.w3.org>) id 1jEyHs-00023R-WA for ietf-http-wg-dist@listhub.w3.org; Thu, 19 Mar 2020 16:44:53 +0000
Resent-Date: Thu, 19 Mar 2020 16:44:52 +0000
Resent-Message-Id: <E1jEyHs-00023R-WA@lyra.w3.org>
Received: from mimas.w3.org ([128.30.52.79]) by lyra.w3.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from <phk@critter.freebsd.dk>) id 1jEyHr-00022b-Jk for ietf-http-wg@listhub.w3.org; Thu, 19 Mar 2020 16:44:51 +0000
Received: from phk.freebsd.dk ([130.225.244.222]) by mimas.w3.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from <phk@critter.freebsd.dk>) id 1jEyHp-0000O3-Lg for ietf-http-wg@w3.org; Thu, 19 Mar 2020 16:44:51 +0000
Received: from critter.freebsd.dk (v-critter.freebsd.dk [192.168.55.3]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by phk.freebsd.dk (Postfix) with ESMTPS id 379071AF10C; Thu, 19 Mar 2020 16:44:37 +0000 (UTC)
Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.15.2/8.15.2) with ESMTPS id 02JGiaXj017528 (version=TLSv1.3 cipher=TLS_AES_256_GCM_SHA384 bits=256 verify=NO); Thu, 19 Mar 2020 16:44:36 GMT (envelope-from phk@critter.freebsd.dk)
Received: (from phk@localhost) by critter.freebsd.dk (8.15.2/8.15.2/Submit) id 02JGiZdX017527; Thu, 19 Mar 2020 16:44:35 GMT (envelope-from phk)
To: Mark Nottingham <mnot@mnot.net>
cc: HTTP Working Group <ietf-http-wg@w3.org>, "Julian F. Reschke" <julian.reschke@greenbytes.de>, Roy Fielding <fielding@gbiv.com>
In-reply-to: <CF788613-EEE1-4321-BE98-780E7C77F607@mnot.net>
From: Poul-Henning Kamp <phk@phk.freebsd.dk>
References: <CF788613-EEE1-4321-BE98-780E7C77F607@mnot.net>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <17525.1584636275.1@critter.freebsd.dk>
Content-Transfer-Encoding: quoted-printable
Date: Thu, 19 Mar 2020 16:44:35 +0000
Message-ID: <17526.1584636275@critter.freebsd.dk>
Received-SPF: pass client-ip=130.225.244.222; envelope-from=phk@critter.freebsd.dk; helo=phk.freebsd.dk
X-W3C-Hub-Spam-Status: No, score=-4.9
X-W3C-Hub-Spam-Report: BAYES_00=-1.9, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, W3C_AA=-1, W3C_IRA=-1, W3C_WL=-1
X-W3C-Scan-Sig: mimas.w3.org 1jEyHp-0000O3-Lg c71573d1059ab39bb243a5bc095371a5
X-Original-To: ietf-http-wg@w3.org
Subject: Re: What we call "headers"
Archived-At: <https://www.w3.org/mid/17526.1584636275@critter.freebsd.dk>
Resent-From: ietf-http-wg@w3.org
X-Mailing-List: <ietf-http-wg@w3.org> archive/latest/37464
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: <https://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 <CF788613-EEE1-4321-BE98-780E7C77F607@mnot.net>, Mark Nottingham wri tes: >A little while back we made some changes in http-core regarding >terminology and headers. This seems to have caused some confusion and >comment, so I thought I'd summarise where I think we're at (Julian and >Roy might want to chime in if they feel differently or want to add >nuance). I appreciate that you are trying to disambiguate the confusion brought about by headers being put in trailers. However, given that we have talked about trailers for 20+ years now, yet they have never gained any serious traction, the simplest and most efficient way to end the confusion is to do away with trailers, so that headers only live in headers, as originally intended. The problems trailers were invented to work around, are barely relevant these days, and almost universally handled with JS on the client. We are not running out of headers, so trailers do not enjoy a "insurance for the future" status like IPv6 did during its twenty years of crossing of the desert. KISS: Trailers must die. -- 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.
- What we call "headers" Mark Nottingham
- Re: What we call "headers" Roy T. Fielding
- Re: What we call "headers" Willy Tarreau
- Re: What we call "headers" Poul-Henning Kamp
- Re: What we call "headers" Mark Nottingham