[quicwg/base-drafts] HTTP Errors aren't consistent (#2231)
ekr <notifications@github.com> Thu, 20 December 2018 23:11 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 1A9ED130F21 for <quic-issues@ietfa.amsl.com>; Thu, 20 Dec 2018 15:11:11 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.447
X-Spam-Level:
X-Spam-Status: No, score=-6.447 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.065, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_IMAGE_ONLY_24=1.618, HTML_MESSAGE=0.001, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001] 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 crSjfFLNHlRe for <quic-issues@ietfa.amsl.com>; Thu, 20 Dec 2018 15:11:08 -0800 (PST)
Received: from out-3.smtp.github.com (out-3.smtp.github.com [192.30.252.194]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7141F131256 for <quic-issues@ietf.org>; Thu, 20 Dec 2018 15:11:07 -0800 (PST)
Date: Thu, 20 Dec 2018 15:11:05 -0800
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1545347465; bh=G6P/0UxUfr10c3uTvkjwCok0NXPwCuUPYG/bAaOVd6k=; h=Date:From:Reply-To:To:Cc:Subject:List-ID:List-Archive:List-Post: List-Unsubscribe:From; b=i6TUqvzsgj96Cbksan8bfmEInMiuPPw8ef7j3zWSAXUq2hGYACuvWCj738mkamDB+ QhazSLuTbX4b4WvxZ7ajn+ZJVAKJHytYGRTKd85tiFMe+sjAuCIKn82Er4KrhrgAqZ H3a/7+1tPSTiv5drJws5iJzEWgKZZjDwIh1gNpBU=
From: ekr <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+0166e4ab946da59bbcdd4c0d6096faec137bd074da99013892cf000000011833e38992a169ce1770750f@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/issues/2231@github.com>
Subject: [quicwg/base-drafts] HTTP Errors aren't consistent (#2231)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5c1c21897f59f_4dc93fe4e8cd45bc1568a0"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: ekr
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/h8r7TmT_zEgvYwp2Arm4lHlb0Tg>
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: Thu, 20 Dec 2018 23:11:12 -0000
Clients don't send GOAWAY and when a client sends one, the server treats it as HTTP_UNEXPECTED_FRAME. By contrast, servers don't send MAX_PUSH_ID but the client treats receiving one as HTTP_MALFORMED_FRAME. By contrast, if GOAWAY is sent on !control it's HTTP_UNEXPECTED_FRAME, but if MAX_PUSH_ID is sent on !control, it's HTTP_WRONG_STREAM. I think the answers here are HTTP_UNEXPECTED_FRAME and HTTP_WRONG_STREAM respectively, but we should be consistent. -- 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/issues/2231