From ietf-http-wg-request+bounce-httpbisa-archive-bis2juki=lists.ie@listhub.w3.org Mon Jan 30 10:36:37 2023 Return-Path: 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 E419DC16B5B5 for ; Mon, 30 Jan 2023 10:36:37 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -4.949 X-Spam-Level: X-Spam-Status: No, score=-4.949 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.25, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H2=-0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_PASS=-0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id MqUYnqBCbb6y for ; Mon, 30 Jan 2023 10:36:34 -0800 (PST) Received: from lyra.w3.org (lyra.w3.org [128.30.52.18]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange ECDHE (P-256) server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 362EDC19E10D for ; Mon, 30 Jan 2023 10:36:33 -0800 (PST) Received: from lists by lyra.w3.org with local (Exim 4.94.2) (envelope-from ) id 1pMYyw-004YNf-6m for ietf-http-wg-dist@listhub.w3.org; Mon, 30 Jan 2023 18:34:18 +0000 Resent-Date: Mon, 30 Jan 2023 18:34:18 +0000 Resent-Message-Id: Received: from www-data by lyra.w3.org with local (Exim 4.94.2) (envelope-from ) id 1pMYyn-004YL0-B6 for ietf-http-wg@listhub.w3.org; Mon, 30 Jan 2023 18:34:09 +0000 Received: from mimas.w3.org ([128.30.52.79]) by lyra.w3.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1pMOti-002hdB-2x for ietf-http-wg@listhub.w3.org; Mon, 30 Jan 2023 07:48:14 +0000 Received: from smtprelay08.ispgateway.de ([134.119.228.98]) by mimas.w3.org with esmtps (TLS1.2) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1pMOtg-00HS2A-JV for ietf-http-wg@w3.org; Mon, 30 Jan 2023 07:48:13 +0000 Received: from [87.78.248.124] (helo=fabiankeil.de) by smtprelay08.ispgateway.de with esmtpsa (TLS1.2) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1pMOuO-0006l0-6A for ietf-http-wg@w3.org; Mon, 30 Jan 2023 08:48:56 +0100 Date: Mon, 30 Jan 2023 08:44:55 +0100 From: Fabian Keil To: ietf-http-wg@w3.org Message-ID: <20230130084455.6ede70c9@fabiankeil.de> In-Reply-To: <16133a2f-5fbe-0f7f-c2ea-e83d20fdb3cc@gmail.com> References: <16133a2f-5fbe-0f7f-c2ea-e83d20fdb3cc@gmail.com> MIME-Version: 1.0 Content-Type: multipart/signed; boundary="Sig_/QeBw4K2KaULkrOf/OLmYGBa"; protocol="application/pgp-signature"; micalg=pgp-sha1 X-Df-Sender: Nzc1MDY3 Received-SPF: none client-ip=134.119.228.98; envelope-from=freebsd-listen@fabiankeil.de; helo=smtprelay08.ispgateway.de X-W3C-Hub-Spam-Status: No, score=-3.9 X-W3C-Hub-Spam-Report: BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H2=-0.001, SPF_HELO_PASS=-0.001, SPF_NONE=0.001, W3C_AA=-1, W3C_WL=-1 X-W3C-Scan-Sig: mimas.w3.org 1pMOtg-00HS2A-JV 2a41ce996b9a89542998d5ed977ad338 X-caa-id: 12f24ff3f8 X-Original-To: ietf-http-wg@w3.org Subject: Re: Slower HTTP for privacy Archived-At: Resent-From: ietf-http-wg@w3.org X-Mailing-List: archive/latest/40719 X-Loop: ietf-http-wg@w3.org Resent-Sender: ietf-http-wg-request@w3.org Precedence: list List-Id: List-Help: List-Post: List-Unsubscribe: --Sig_/QeBw4K2KaULkrOf/OLmYGBa Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: quoted-printable "Soni L." wrote on 2023-01-29 at 11:45:53: > It would be appreciated if there were a slower HTTP, with more round=20 > trips, explicitly designed with privacy negotiation in mind. >=20 > Importantly, you can't leak data which you do not have. The best way to=20 > not have that data is to not receive it. >=20 > Why does a server need to accept user agents and a bunch of other=20 > unnecessary stuff if it isn't gonna use it? Doesn't it just make the=20 > server more liable for no good reason? Make it possible to turn it off!=20 > Most of it can just be turned off. >=20 > In fact, the simplest servers (static hosting) only really need the URL=20 > and the Host. Everything else is unnecessary liability. It's not exactly what you ask for, but Privoxy [0] has a delay-response{} response action [1] that is somewhat related. Fabian [0] [1] --Sig_/QeBw4K2KaULkrOf/OLmYGBa Content-Type: application/pgp-signature Content-Description: OpenPGP digital signature -----BEGIN PGP SIGNATURE----- iF0EARECAB0WIQTKUNd6H/m3+ByGULIFiohV/3dUnQUCY9d1eAAKCRAFiohV/3dU nWV5AKDMCvn2cqO1ws+U4BYWVFvv6fzx1QCgtAOTh3FGVOBTYzeo3bklV1564dM= =3H9Z -----END PGP SIGNATURE----- --Sig_/QeBw4K2KaULkrOf/OLmYGBa--