Re: [quicwg/base-drafts] HTTP error codes use inconsistent language (#2765)

Mike Bishop <> Wed, 28 August 2019 19:48 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id CF8911200D6 for <>; Wed, 28 Aug 2019 12:48:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -7.999
X-Spam-Status: No, score=-7.999 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_32=0.001, HTML_MESSAGE=0.001, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, SPF_HELO_NONE=0.001, 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 5waaEgVjqj8g for <>; Wed, 28 Aug 2019 12:48:23 -0700 (PDT)
Received: from ( []) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 343E2120091 for <>; Wed, 28 Aug 2019 12:48:23 -0700 (PDT)
Date: Wed, 28 Aug 2019 12:48:22 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=pf2014; t=1567021702; bh=5zLG6yPr0CvLRvj3jAC/gSV/LIqnOf9aSgYZijFbTYM=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=qMwIPiofgedEfnIMDXCdPGJj8F+9mXjotLkF90MBpozBbCglV1mQNcJ4Xfo2bk+Sz sM7hhsRrzJFzqDZOeZdiXOU1SFVr1p48SRd2QHA0xxUPR6fKT3UfxkX4rtmZJ48X4S 8YmJxxRFm5mEswoMm7O+Wt5YPiu4kS5sIddD1G3g=
From: Mike Bishop <>
Reply-To: quicwg/base-drafts <>
To: quicwg/base-drafts <>
Cc: Subscribed <>
Message-ID: <quicwg/base-drafts/issues/2765/>
In-Reply-To: <quicwg/base-drafts/issues/>
References: <quicwg/base-drafts/issues/>
Subject: Re: [quicwg/base-drafts] HTTP error codes use inconsistent language (#2765)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5d66da8623972_29333fdc0b6cd9601492647"; 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
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: Wed, 28 Aug 2019 19:48:25 -0000

The different value-judgement terms are corrected by the flurry of settings PRs that @LPardue already did.  HTTP_FRAME_ERROR has replaced malformed, and UNEXPECTED_FRAME and WRONG_STREAM are reasonably descriptive (though see #2809, #2996).

We do still have some variation between HTTP_THING_DESCRIPTOR, HTTP_THING_ERROR, and HTTP_DESCRIPTOR_THING (e.g. HTTP_UNEXPECTED_FRAME versus HTTP_REQUEST_REJECTED) that might be worth reconciling.

Is it worth turning into HTTP_FRAME_UNEXPECTED?

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