Re: How big can the protocol elements in HTTP be?
Michael Sweet <msweet@msweet.org> Fri, 25 October 2024 15:27 UTC
Received: by ietfa.amsl.com (Postfix) id 7146FC1840FD; Fri, 25 Oct 2024 08:27:35 -0700 (PDT)
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 70AD8C180B6A for <ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com>; Fri, 25 Oct 2024 08:27:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.856
X-Spam-Level:
X-Spam-Status: No, score=-2.856 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HEADER_FROM_DIFFERENT_DOMAINS=0.25, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_BLOCKED=0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, 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=w3.org header.b="ad3CHIBF"; dkim=pass (2048-bit key) header.d=w3.org header.b="NShppPcO"; dkim=pass (1024-bit key) header.d=msweet.org header.b="aviN6Lr8"
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 LY_Zaa_D_gGZ for <ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com>; Fri, 25 Oct 2024 08:27:31 -0700 (PDT)
Received: from mab.w3.org (mab.w3.org [IPv6:2600:1f18:7d7a:2700:d091:4b25:8566:8113]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange ECDHE (P-256) server-signature ECDSA (P-256) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 76380C1840F0 for <httpbisa-archive-bis2Juki@ietf.org>; Fri, 25 Oct 2024 08:27:31 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=w3.org; s=s1; h=Subject:To:References:Message-Id:Cc:Date:In-Reply-To:From: Mime-Version:Content-Type:Reply-To; bh=eGl/JDUswFoXAsiYKdgy8qbIpWgV0ed1Te3i5EALcFQ=; b=ad3CHIBF9q7lzwhyG6G975DzPL 72K10NpCukDReBeOmRugSC8XHF2WjPv+FFG8OSFBsYztuVTLmiNoiT3DUfL/U3PBijffBD5hFa5UU mQNUplf5jpRNtvOC+WHJrKegCAZzR/mOTxtl/5NtCddiICOwSDvBs60bjIBDyTqEhu25RkrEGXKKr G26lAqXyKJWsGPYklV99f9vSYoIDAZ41w3/1o49ZkiKuvERI8hlDl4twvCXh8KqY/5bVZmjCPAxXl pOGxl4GV57T1WZPxDevDsoq1USmeeQEM1lL4wVXcyylQm157nSiLJ8lpUGcF7je30XQBEGYFgG2Ai TUoBIvXA==;
Received: from lists by mab.w3.org with local (Exim 4.96) (envelope-from <ietf-http-wg-request@listhub.w3.org>) id 1t4MD6-0006OC-33 for ietf-http-wg-dist@listhub.w3.org; Fri, 25 Oct 2024 15:26:44 +0000
Resent-Date: Fri, 25 Oct 2024 15:26:44 +0000
Resent-Message-Id: <E1t4MD6-0006OC-33@mab.w3.org>
Received: from ip-10-0-0-144.ec2.internal ([10.0.0.144] helo=pan.w3.org) by mab.w3.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.96) (envelope-from <msweet@msweet.org>) id 1t4MD4-0006NC-2P for ietf-http-wg@listhub.w3.internal; Fri, 25 Oct 2024 15:26:42 +0000
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=w3.org; s=s1; h=To:References:Message-Id:Cc:Date:In-Reply-To:From:Subject: Mime-Version:Content-Type:Reply-To; bh=eGl/JDUswFoXAsiYKdgy8qbIpWgV0ed1Te3i5EALcFQ=; t=1729870002; x=1730734002; b=NShppPcO6a/QrePr4rj3zWOhEzRWUlFzmQck12e9QUCOpsDlCHdhTC+WCdrD58x0dlRhBsleo/G p7tELD7Vzo+4fvH+4W93/A5zH2RWs/BmdcztQNVfqMCnqTeJQ5g4o9RwijwgjJf2SrlTmSzdqqlyW 1AGWWL6eSOBsui6lFXvU1Qow98K36L9c/cRktwMU+6z3l3uemccduoIRkS+/TKJMprEw2no5bv1lm Z8PsV5GuJEF/Cq3El3mIBft4Qe3SPqL5nrMSfwnm6Xoh+qxm+KJi3TpwYj5K6xHlgINQ5mqy1PeWc zSmwWZu1yRdYnmCTrJ6LhKCGcsZYO6WX4FMQ==;
Received-SPF: pass (pan.w3.org: domain of msweet.org designates 173.255.209.91 as permitted sender) client-ip=173.255.209.91; envelope-from=msweet@msweet.org; helo=mail.msweet.org;
Received: from mail.msweet.org ([173.255.209.91]) by pan.w3.org with esmtps (TLS1.2) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.96) (envelope-from <msweet@msweet.org>) id 1t4MD4-00CqPy-0c for ietf-http-wg@w3.org; Fri, 25 Oct 2024 15:26:42 +0000
Received: from smtpclient.apple (cbl-66-186-76-47.vianet.ca [66.186.76.47]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.msweet.org (Postfix) with ESMTPSA id D758980F08; Fri, 25 Oct 2024 15:26:37 +0000 (UTC)
DKIM-Filter: OpenDKIM Filter v2.11.0 mail.msweet.org D758980F08
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=msweet.org; s=default; t=1729869998; bh=9P9+jopC76CDitwi3hVsK6CbZsrLLezmSohWyuNkYoc=; h=Subject:From:In-Reply-To:Date:Cc:References:To:From; b=aviN6Lr8JkEllQ1ScoGNxVHCyTxMNPqwo8i74IVRJF9hZsl3jKNjwEmkiZMDoqBB/ eRCyTxjs4/NMqDqwtFdC06qxWHJBg6hr4UaZd0svbZH2xsMGqwO6qgLrvte760av6l VVlcPZi/cJZionkZUBQUWpZob3o0grFnQWt7UQiQ=
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3826.200.121\))
From: Michael Sweet <msweet@msweet.org>
In-Reply-To: <b6f5a57a-b03c-4ff8-a4fb-9a1e3369f47a@betaapp.fastmail.com>
Date: Fri, 25 Oct 2024 11:26:26 -0400
Cc: ietf-http-wg@w3.org
Content-Transfer-Encoding: quoted-printable
Message-Id: <B63ED571-280E-4006-83C0-CC638C4813E3@msweet.org>
References: <b6f5a57a-b03c-4ff8-a4fb-9a1e3369f47a@betaapp.fastmail.com>
To: Martin Thomson <mt@lowentropy.net>
X-Mailer: Apple Mail (2.3826.200.121)
X-W3C-Hub-DKIM-Status: validation passed: (address=msweet@msweet.org domain=msweet.org), signature is good
X-W3C-Hub-Spam-Status: No, score=-4.1
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, DMARC_PASS=-0.001, RCVD_IN_DNSWL_BLOCKED=0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, W3C_AA=-1, W3C_WL=-1
X-W3C-Scan-Sig: pan.w3.org 1t4MD4-00CqPy-0c 3cbb229ee2fea077cee559877a93045b
X-Original-To: ietf-http-wg@w3.org
Subject: Re: How big can the protocol elements in HTTP be?
Archived-At: <https://www.w3.org/mid/B63ED571-280E-4006-83C0-CC638C4813E3@msweet.org>
Resent-From: ietf-http-wg@w3.org
X-Mailing-List: <ietf-http-wg@w3.org> archive/latest/52478
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/email/>
List-Post: <mailto:ietf-http-wg@w3.org>
List-Unsubscribe: <mailto:ietf-http-wg-request@w3.org?subject=unsubscribe>
Martin, > On Oct 25, 2024, at 6:44 AM, Martin Thomson <mt@lowentropy.net> wrote: > ... > How big can a URI scheme be? RFC 3986 doesn't say. 8k for that seems a bit much. The registry has some long ones though, so maybe I could be conservative and say 256 bytes. FWIW, IPP caps "uriScheme" values to 63 bytes, which should be good given that the longest registered URI scheme is 36 bytes and we've had that limit in place for 26 years now... :) ________________________ Michael Sweet
- How big can the protocol elements in HTTP be? Martin Thomson
- Re: How big can the protocol elements in HTTP be? Willy Tarreau
- Re: How big can the protocol elements in HTTP be? Michael Sweet