Re: Slower HTTP for privacy
"Soni L." <fakedme+http@gmail.com> Mon, 30 January 2023 21:42 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 64E3BC151552 for <ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com>; Mon, 30 Jan 2023 13:42:17 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.748
X-Spam-Level:
X-Spam-Status: No, score=-2.748 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HEADER_FROM_DIFFERENT_DOMAINS=0.25, HTML_MESSAGE=0.001, MAILING_LIST_MULTI=-1, NICE_REPLY_A=-0.001, RCVD_IN_MSPIKE_H2=-0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 xN6OEuVBS5je for <ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com>; Mon, 30 Jan 2023 13:42:13 -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 4751EC14F6EC for <httpbisa-archive-bis2Juki@lists.ietf.org>; Mon, 30 Jan 2023 13:42:12 -0800 (PST)
Received: from lists by lyra.w3.org with local (Exim 4.94.2) (envelope-from <ietf-http-wg-request@listhub.w3.org>) id 1pMbua-005XV5-R1 for ietf-http-wg-dist@listhub.w3.org; Mon, 30 Jan 2023 21:42:00 +0000
Resent-Date: Mon, 30 Jan 2023 21:42:00 +0000
Resent-Message-Id: <E1pMbua-005XV5-R1@lyra.w3.org>
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 <fakedme+http@gmail.com>) id 1pMbuY-005XTs-Qs for ietf-http-wg@listhub.w3.org; Mon, 30 Jan 2023 21:41:58 +0000
Received: from mail-oo1-xc2b.google.com ([2607:f8b0:4864:20::c2b]) by mimas.w3.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from <fakedme+http@gmail.com>) id 1pMbuX-000BFZ-65 for ietf-http-wg@w3.org; Mon, 30 Jan 2023 21:41:58 +0000
Received: by mail-oo1-xc2b.google.com with SMTP id b10-20020a4a9fca000000b004e6f734c6b4so1441588oom.9 for <ietf-http-wg@w3.org>; Mon, 30 Jan 2023 13:41:56 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=in-reply-to:from:references:cc:to:content-language:subject :user-agent:mime-version:date:message-id:sender:from:to:cc:subject :date:message-id:reply-to; bh=RsZxPRqfOiXcL+C7VwJcGILKfLJPYuT2CXmsIESaa00=; b=dxvbKVA+LCoeqN70YFJ1P9RGTgxIaNWjRzemjScwRNuGAVvN1ngIPc5xGP1rY4hDL+ U/E/8Ntr+ZnweDm/I1jcP0si9/8TkhtZBntgHAVZB/p/ZcM0352i7lFXGUyd0JjU0iam t4wH5DVz5p8Fcx958GVhr0tpfsLx9CEAxEJViQj35dj0jjWeJ+YUGHf+O0xexJKf42FR BTBgTPkKZpWioychdHtaS+moCwEuSGUFZ8qAy2OFKmyOG9GSTp20YJxG7xCGT2fb/Oj2 8Zg0nzB3easPhywXl8A71G7CVdio2Ufa7lmL3xLn32RyA+TW2AU8z7G6g9p4pVi1K9Ot LUJw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=in-reply-to:from:references:cc:to:content-language:subject :user-agent:mime-version:date:message-id:sender:x-gm-message-state :from:to:cc:subject:date:message-id:reply-to; bh=RsZxPRqfOiXcL+C7VwJcGILKfLJPYuT2CXmsIESaa00=; b=UHR+ETMQ5j6MBs22tK+JS2RNAnJkPlmBCC1RbmBk1ay/OyqnyxS1KEf1JkCb4Pbyt6 Rl0PkSo+tFgUHJVj91kU3Ml30R9LW4CWVV5/wvupF0Z+fyJ59q2/YsOsWJGGpeS4q1L4 1RfFM0NIZz3Gw5AaUi7IWD5jbseh5SUPAXm25/BGD2qvRFLKB/5Sh01u0JTWtyUipfa8 wCJLeaDf3OwD/CVse1/u4gkFu8ITpAN6zJZ9thkOZCN5v4D3XTyHYp0Hlw8C6UuDlFZ7 0Vjg/adLsfsj49WAgAgidTlmp/cFQ0PjGJoUbjLIQrX0jEUQxmdeSX1tprkadrK3hMYi i1Ow==
X-Gm-Message-State: AO0yUKUX1ogxuKSnkfFKxvRQDKDgO5XGwtmdC9v7EtYV/VYR6JF571o7 mXakkPMFSCjzCX6ENxbS9uo=
X-Google-Smtp-Source: AK7set8BqTWG68RM49b9AluXhAtmvgf1WylIa0WgeZYQul67jgL1KjqCs4KW8K2i+j6RuhqGvvYLxg==
X-Received: by 2002:a05:6820:1a9e:b0:4a3:fbd7:c32a with SMTP id bt30-20020a0568201a9e00b004a3fbd7c32amr4746885oob.2.1675114906222; Mon, 30 Jan 2023 13:41:46 -0800 (PST)
Received: from ?IPV6:2804:431:cfcc:25b6::536f:6e69? ([2804:431:cfcc:25b6::536f:6e69]) by smtp.googlemail.com with ESMTPSA id e79-20020a4a5552000000b0051765eb8c25sm2342527oob.10.2023.01.30.13.41.45 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Mon, 30 Jan 2023 13:41:45 -0800 (PST)
Sender: "Soni L." <fakedme@gmail.com>
Content-Type: multipart/alternative; boundary="------------O8WAsicvywnUE2XC2hWrklQc"
Message-ID: <eb8e0e06-6515-c1d5-bee7-edc3ed92ff22@gmail.com>
Date: Mon, 30 Jan 2023 18:41:42 -0300
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 Thunderbird/102.7.0
Content-Language: en-US
To: Nick Harper <ietf@nharper.org>
Cc: ietf-http-wg@w3.org
References: <16133a2f-5fbe-0f7f-c2ea-e83d20fdb3cc@gmail.com> <20230130084455.6ede70c9@fabiankeil.de> <5d420b68-e4b2-34b8-1a56-a9fddf9872a0@gmail.com> <CACcvr=kxp7gGgUFtPHoZxO4vifJ=J1ipyyJz9RxtZskm0RWDkg@mail.gmail.com>
From: "Soni L." <fakedme+http@gmail.com>
In-Reply-To: <CACcvr=kxp7gGgUFtPHoZxO4vifJ=J1ipyyJz9RxtZskm0RWDkg@mail.gmail.com>
Received-SPF: pass client-ip=2607:f8b0:4864:20::c2b; envelope-from=fakedme+http@gmail.com; helo=mail-oo1-xc2b.google.com
X-W3C-Hub-DKIM-Status: validation passed: (address=fakedme+http@gmail.com domain=gmail.com), signature is good
X-W3C-Hub-Spam-Status: No, score=-3.2
X-W3C-Hub-Spam-Report: BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, FREEMAIL_REPLY=1, HTML_MESSAGE=0.001, NICE_REPLY_A=-0.09, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, W3C_AA=-1, W3C_WL=-1
X-W3C-Scan-Sig: mimas.w3.org 1pMbuX-000BFZ-65 c3c5c6ed1bfd4932fdfb81c100de5437
X-Original-To: ietf-http-wg@w3.org
Subject: Re: Slower HTTP for privacy
Archived-At: <https://www.w3.org/mid/eb8e0e06-6515-c1d5-bee7-edc3ed92ff22@gmail.com>
Resent-From: ietf-http-wg@w3.org
X-Mailing-List: <ietf-http-wg@w3.org> archive/latest/40722
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>
On 1/30/23 18:27, Nick Harper wrote: > It sounds like what you want is Client Hints > (https://developer.mozilla.org/en-US/docs/Web/HTTP/Client_hints) Roughly, but it still doesn't eliminate the existing headers altogether. Client Hints seems to be *positive* hints only, i.e. "send these, please". What about *negative* hints, i.e. "don't even bother sending these"? How do you prevent useless data from being sent? > > On Mon, Jan 30, 2023 at 10:48 AM Soni L. <fakedme+http@gmail.com > <mailto:fakedme%2Bhttp@gmail.com>> wrote: > > > > On 1/30/23 04:44, Fabian Keil wrote: > > "Soni L." <fakedme+http@gmail.com > <mailto:fakedme%2Bhttp@gmail.com>> wrote on 2023-01-29 at 11:45:53: > > > > > It would be appreciated if there were a slower HTTP, with more > round > > > trips, explicitly designed with privacy negotiation in mind. > > > > > > Importantly, you can't leak data which you do not have. The > best way to > > > not have that data is to not receive it. > > > > > > Why does a server need to accept user agents and a bunch of other > > > unnecessary stuff if it isn't gonna use it? Doesn't it just > make the > > > server more liable for no good reason? Make it possible to > turn it off! > > > Most of it can just be turned off. > > > > > > In fact, the simplest servers (static hosting) only really > need the URL > > > 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] <https://www.privoxy.org/> > > [1] > <https://www.privoxy.org/user-manual/actions-file.html#DELAY-RESPONSE> > It's not at all what we ask for! Uh, we mean like, why does the HTTP > server have to parse and discard the User-Agent header and another > 10 or > so headers which it has no use for, instead of just... not receiving > those headers in the first place? > > Why can't the client send URL and Host, then wait for the server > to send > a Headers Required message, then send the required headers (which > may be > none)? Yes, it takes longer (more RTTs), but the best way to improve > privacy is to not have the data in the first place. >
- Slower HTTP for privacy Soni L.
- Re: Slower HTTP for privacy Fabian Keil
- Re: Slower HTTP for privacy Soni L.
- Re: Slower HTTP for privacy Nick Harper
- Re: Slower HTTP for privacy Soni L.
- Re: Slower HTTP for privacy Daniel Stenberg
- Re: Slower HTTP for privacy Jeffrey Yasskin