[quicwg/base-drafts] Why do I have to explicitly cancel after GOAWAY (#2226)
ekr <notifications@github.com> Thu, 20 December 2018 23:06 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 E1F40130F21 for <quic-issues@ietfa.amsl.com>; Thu, 20 Dec 2018 15:06:39 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.661
X-Spam-Level:
X-Spam-Status: No, score=-6.661 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_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: 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 4QuG553Oj8Tb for <quic-issues@ietfa.amsl.com>; Thu, 20 Dec 2018 15:06:37 -0800 (PST)
Received: from out-4.smtp.github.com (out-4.smtp.github.com [192.30.252.195]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 348E1131257 for <quic-issues@ietf.org>; Thu, 20 Dec 2018 15:06:37 -0800 (PST)
Date: Thu, 20 Dec 2018 15:06:35 -0800
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1545347195; bh=+VqiG5T45t5XGLgMJ/kO0e+DoLt0WpsD4xagwRwd7GE=; h=Date:From:Reply-To:To:Cc:Subject:List-ID:List-Archive:List-Post: List-Unsubscribe:From; b=mBwcEkKBQnVqqHWi41ZVMuHRZsvvhlmd62S64c/coO7L36KQQRjQNeQjWmwua/2Cl NLPYDwzkKLgqF5Ymr+UH36qINveuhSjvYZJj0XdUO8yzYvSE+dOoHwiwyyvwBhRcth YOLPm+9+pqaYJrKmd1k2cdQQg8pm5cTc4AKmzbA8=
From: ekr <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+0166e4abfdbdfbd9d49643136d53192c0f00bb7da4fa612992cf000000011833e27b92a169ce17707020@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/issues/2226@github.com>
Subject: [quicwg/base-drafts] Why do I have to explicitly cancel after GOAWAY (#2226)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5c1c207b8d863_1be63fddd64d45c4128827"; 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/04Q_DnN0xlJ9IHdASgRRn36UD0U>
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:06:40 -0000
Why do I have to explicitly cancel after GOAWAY?
```
Once GOAWAY is sent, the server MUST cancel requests sent on streams with an
identifier higher than the indicated last Stream ID. Clients MUST NOT send new
requests on the connection after receiving GOAWAY, although requests might
already be in transit. A new connection can be established for new requests.
If the client has sent requests on streams with a higher Stream ID than
indicated in the GOAWAY frame, those requests are considered cancelled
({{request-cancellation}}). Clients SHOULD reset any streams above this ID with
the error code HTTP_REQUEST_CANCELLED. Servers MAY also cancel requests on
streams below the indicated ID if these requests were not processed.
```
Given that GOAWAY already tells the client this, what's the point?
--
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/2226