Re: [quicwg/base-drafts] What if server does not send HTTP_EARLY_RESPONSE but starts sending response (#2963)

ianswett <notifications@github.com> Tue, 15 October 2019 19:36 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 2FBA612004A for <quic-issues@ietfa.amsl.com>; Tue, 15 Oct 2019 12:36:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.382
X-Spam-Level:
X-Spam-Status: No, score=-6.382 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_24=1.618, 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: 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 KhcQvIG2P-7s for <quic-issues@ietfa.amsl.com>; Tue, 15 Oct 2019 12:36:01 -0700 (PDT)
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 49097120046 for <quic-issues@ietf.org>; Tue, 15 Oct 2019 12:36:01 -0700 (PDT)
Received: from github-lowworker-2e54e43.va3-iad.github.net (github-lowworker-2e54e43.va3-iad.github.net [10.48.17.27]) by smtp.github.com (Postfix) with ESMTP id 6992C2C1F6D for <quic-issues@ietf.org>; Tue, 15 Oct 2019 12:36:00 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1571168160; bh=mt6vZ7comnqhzYXscgVbkha/6g+FK573fchBi0rnqbA=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=lSFJHkJTcRNTiGas+QDqkceOcXTU3b5CIzGD/GPrJEYRXC2EV35gCPh8CLtlr2bZ/ 3YpfUM8MRMSsJJqlR0nUys0Wi2Soprd7HoHTgyuOuW0lq/azkXlme22k3MEsxJNs/+ GaB4Od+4buQDWfPlqppFd8u9f3rTcNTi9sGYifKY=
Date: Tue, 15 Oct 2019 12:36:00 -0700
From: ianswett <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+AFTOJK7EQZCLZOVA2K7VH6F3WNQDBEVBNHHBZDNRFQ@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/issues/2963/542370874@github.com>
In-Reply-To: <quicwg/base-drafts/issues/2963@github.com>
References: <quicwg/base-drafts/issues/2963@github.com>
Subject: Re: [quicwg/base-drafts] What if server does not send HTTP_EARLY_RESPONSE but starts sending response (#2963)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5da61fa05a0f5_47893f8659acd96471523f"; charset=UTF-8
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: ianswett
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/gxqH_YKPxQYne_fcgKWAtqnOnEI>
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, 15 Oct 2019 19:36:04 -0000

The text is now:

> A server can send a complete response prior to the client sending an
   entire request if the response does not depend on any portion of the
   request that has not been sent and received.  When this is true, a
   server MAY abort reading the request stream with error code
   HTTP_EARLY_RESPONSE, send a complete response, and cleanly close the
   sending part of the stream.  Clients MUST NOT discard complete
   responses as a result of having their request terminated abruptly,
   though clients can always discard responses at their discretion for
   other reasons.

-- 
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/2963#issuecomment-542370874