Re: [quicwg/base-drafts] Interaction of FIN and message parsing (#2003)

Mike Bishop <notifications@github.com> Mon, 26 November 2018 22: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 2B4FD131016 for <quic-issues@ietfa.amsl.com>; Mon, 26 Nov 2018 14:11:20 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.46
X-Spam-Level:
X-Spam-Status: No, score=-9.46 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-1.46, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, 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 Qz4JeA7mnrh5 for <quic-issues@ietfa.amsl.com>; Mon, 26 Nov 2018 14:11:19 -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 D3AF7130DDB for <quic-issues@ietf.org>; Mon, 26 Nov 2018 14:11:18 -0800 (PST)
Date: Mon, 26 Nov 2018 14:11:17 -0800
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1543270277; bh=/LclnZuMsYbKmFrh/79wtOTZHdVqP1xRgkfRYAfxriw=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=koo2UB/btDBy4OlWJ7j8m87u4EKdimgslvZKJxapB0+4tSWAefuZjki/aWM2507R6 UMGa3qegf5J7RCzTtFtqUxLK8eqOyyYsrsCI6//FebthzUqvtIppI+BnW+gaW3ADKL hUO1UuZ5BqpFndB6w9btl58ri0T6VMpEQeHciugA=
From: Mike Bishop <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+0166e4ab99fefc8b30edc4b1b38647140ca2336a28a4b5e492cf000000011814318592a169ce16b355af@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/pull/2003/c441819089@github.com>
In-Reply-To: <quicwg/base-drafts/pull/2003@github.com>
References: <quicwg/base-drafts/pull/2003@github.com>
Subject: Re: [quicwg/base-drafts] Interaction of FIN and message parsing (#2003)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5bfc6f85edb38_3a463fb1c0ad45c4930c5"; 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
X-GitHub-Recipient-Address: quic-issues@ietf.org
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic-issues/nNVLHCHZOCDebCdh6j5LqqET6Kc>
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: Mon, 26 Nov 2018 22:11:20 -0000

Formally, the data transferred on the TCP connection is the body of the HTTP request, so it's not a special flower in that sense.  But it's special in that it's the only case where the server MUST process the headers before the end of the "message."

The requirement that the client MUST NOT make FIN dependent on receiving anything would be a good wording improvement.

-- 
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/pull/2003#issuecomment-441819089