From mboxrd@z Thu Jan 1 00:00:00 1970 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on inbox.vuxu.org X-Spam-Level: X-Spam-Status: No, score=0.0 required=5.0 tests=none autolearn=ham autolearn_force=no version=3.4.4 Received: (qmail 22917 invoked from network); 11 Jan 2021 17:44:06 -0000 Received: from 1ess.inri.net (216.126.196.35) by inbox.vuxu.org with ESMTPUTF8; 11 Jan 2021 17:44:06 -0000 Received: from mimir.eigenstate.org ([206.124.132.107]) by 1ess; Mon Jan 11 12:13:49 -0500 2021 Received: from abbatoir.fios-router.home (pool-74-101-2-6.nycmny.fios.verizon.net [74.101.2.6]) by mimir.eigenstate.org (OpenSMTPD) with ESMTPSA id a9fb9040 (TLSv1.2:ECDHE-RSA-AES256-SHA:256:NO) for <9front@9front.org>; Mon, 11 Jan 2021 09:13:38 -0800 (PST) Message-ID: <11338093C416F93FBE18D91448174F66@eigenstate.org> To: 9front@9front.org Date: Mon, 11 Jan 2021 09:13:36 -0800 From: ori@eigenstate.org In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit List-ID: <9front.9front.org> List-Help: X-Glyph: ➈ X-Bullshit: hosting property scripting backend Subject: Re: [9front] [PATCH] webfs: add 'headers' file Reply-To: 9front@9front.org Precedence: bulk Quoth Steve Simon : > I have a memory that webfs already creates header files for a limited set of headers: contenttype, contentencoding, length (from memory). why not just export headers we need so there can never be a clash? How does webfs know which headers we need in advance? lots of software adds magic or custom headers these days.