IETF Logo Mail Archive

Re: [quicwg/base-drafts] Discuss max-header-list-size from the other side (#2774)

Mike Bishop <notifications@github.com> Tue, 11 June 2019 23:42 UTC

Return-Path: <noreply@github.com>
X-Original-To: quic-issues@ietfa.amsl.com
Delivered-To: quic-issues@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8A24E12004C for <quic-issues@ietfa.amsl.com>; Tue, 11 Jun 2019 16:42:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.605
X-Spam-Level:
X-Spam-Status: No, score=-6.605 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_IMAGE_ONLY_28=1.404, HTML_MESSAGE=0.001, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=github.com
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 dWUqYSo3fKxR for <quic-issues@ietfa.amsl.com>; Tue, 11 Jun 2019 16:42:06 -0700 (PDT)
Received: from out-11.smtp.github.com (out-11.smtp.github.com [192.30.254.194]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 01F1812001E for <quic-issues@ietf.org>; Tue, 11 Jun 2019 16:42:06 -0700 (PDT)
Date: Tue, 11 Jun 2019 16:42:05 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1560296525; bh=sC2govuaNVoCxIq8i45Px/KZ4eIPW78EDUwW2Z4y2B8=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=DIhTCi3fQojqS4AzNdWEhP89MTuoFBYlp5kLXt1L0qkn9TXxhtt3cbsycJYd2C1AO b9lMjzw+m+uwnxMrvHCJKf6Uiq1zxsZhwI4w8lzLU0SW3xSY5EbxDG4zPhLoyDUCUE 4Rrg2swW+4KIaxjI/SjXJq6cdI6LFeVHle3flDDY=
From: Mike Bishop <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+AFTOJK7TNZXRSAUVRWFWM2F3BVXM3EVBNHHBWAXMNE@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/pull/2774/c501064228@github.com>
In-Reply-To: <quicwg/base-drafts/pull/2774@github.com>
References: <quicwg/base-drafts/pull/2774@github.com>
Subject: Re: [quicwg/base-drafts] Discuss max-header-list-size from the other side (#2774)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5d003c4d4a49c_6e833fdd158cd96c65412"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: MikeBishop
X-GitHub-Recipient: quic-issues
X-GitHub-Reason: subscribed
X-Auto-Response-Suppress: All
X-GitHub-Recipient-Address: quic-issues@ietf.org
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic-issues/VRtR3W3jDz91btWIgMpp8NKVIqk>
X-BeenThere: quic-issues@ietf.org
X-Mailman-Version: 2.1.29
List-Id: Notification list for GitHub issues related to the QUIC WG <quic-issues.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/quic-issues>, <mailto:quic-issues-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/quic-issues/>
List-Post: <mailto:quic-issues@ietf.org>
List-Help: <mailto:quic-issues-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/quic-issues>, <mailto:quic-issues-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 11 Jun 2019 23:42:08 -0000

> I'm still confused by this paragraph, it opens with discussion of the header (emphasis mine):
> 
> > An HTTP/3 implementation MAY impose a limit on the maximum size of **the header** it will accept on an individual HTTP message
> 
> Since the rest of the paragraph discusses SETTINGS_MAX_HEADER_LIST_SIZE it seems that the limit only applies to the sum total of all header fields in a message. It is not possible to express the maximum size of a single header field. If so, we should change the wording slightly to make this clearer.

The message header consists of a sequence header fields.  The limit is on the full size of the message header, not any one field.  There's ongoing discussion in http-core about how best to accommodate the colloquial usage of "header" to refer to an individual field.

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/quicwg/base-drafts/pull/2774#issuecomment-501064228

v2.23.0 | Report a Bug | By Email