Re: [quicwg/base-drafts] all HTTP/3 protocol violations should lead to connection errors (#2510)

Dmitri Tikhonov <> Mon, 11 March 2019 20:28 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 2D1A212787F for <>; Mon, 11 Mar 2019 13:28:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -6.597
X-Spam-Status: No, score=-6.597 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.001, 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_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: (amavisd-new); dkim=pass (1024-bit key)
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id nHE2jYtYw07l for <>; Mon, 11 Mar 2019 13:28:11 -0700 (PDT)
Received: from ( []) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id DA6CA1200D8 for <>; Mon, 11 Mar 2019 13:28:10 -0700 (PDT)
Date: Mon, 11 Mar 2019 13:28:10 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=pf2014; t=1552336090; bh=VyqobbWz6Bw9+ma+8MhcD4zymv8Qc/mwkp3EAYLouNs=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=gFrarjR83/a3ApMPchcP6DNPdhwTm7CtbHGKdMFMhSA12PgMhxEE7cklYCwPiHWCq so8W6E1Lr2tcC/2K0cos6QItY22uXfV8EhpVZl6rE6JLp7M1lh1jg1KZmkZB/RiTQ8 LwpXFJ06oDf2S9LCyPOuYL1oxbt+z/w4ggJ+ub3c=
From: Dmitri Tikhonov <>
Reply-To: quicwg/base-drafts <>
To: quicwg/base-drafts <>
Cc: Subscribed <>
Message-ID: <quicwg/base-drafts/pull/2510/>
In-Reply-To: <quicwg/base-drafts/pull/>
References: <quicwg/base-drafts/pull/>
Subject: Re: [quicwg/base-drafts] all HTTP/3 protocol violations should lead to connection errors (#2510)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5c86c4da29644_3fba3fabb7ed45c0323d9"; charset=UTF-8
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: dtikhonov
X-GitHub-Recipient: quic-issues
X-GitHub-Reason: subscribed
X-Auto-Response-Suppress: All
Archived-At: <>
X-Mailman-Version: 2.1.29
List-Id: Notification list for GitHub issues related to the QUIC WG <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Mon, 11 Mar 2019 20:28:12 -0000

The clients already differ in many, many other ways.  The size check is trivial, but that's not the problem.  The problem is the risk of breaking existing web applications.  The current HTTP/2 browser behavior is to advertise a limit, but to process much larger header lists.  We don't want to end up where *"HTTP/3 broke my app!"* is a thing.

You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub: