IETF Logo Mail Archive

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

martinduke <notifications@github.com> Tue, 27 November 2018 02:50 UTC

Return-Path: <bounces+848413-a050-quic-issues=ietf.org@sgmail.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 94E6E130E1E for <quic-issues@ietfa.amsl.com>; Mon, 26 Nov 2018 18:50:15 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.46
X-Spam-Level:
X-Spam-Status: No, score=-4.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_NONE=-0.0001, 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 SHvSiz_UsuRx for <quic-issues@ietfa.amsl.com>; Mon, 26 Nov 2018 18:50:13 -0800 (PST)
Received: from o4.sgmail.github.com (o4.sgmail.github.com [192.254.112.99]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5D6DF130E33 for <quic-issues@ietf.org>; Mon, 26 Nov 2018 18:50:13 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=github.com; h=from:reply-to:to:cc:in-reply-to:references:subject:mime-version:content-type:content-transfer-encoding:list-id:list-archive:list-post:list-unsubscribe; s=s20150108; bh=sHpjcsJt9xj2cvLEweQAe9prDMo=; b=fsxXl63UDxBa35xD TgwspagTBZIxIgwbIYXz842+rCLfJTlkgtLELUi44BMVLcICrw5nxN+6isp7uO8l VdVdw/IoQ6Gn9JDTTo9p55RRMPX7MFmMaZyfH5UqobYEmxHh1bibkek9/ikZBNH4 yOhUK7flcssgSLlMcR30MXvwYGk=
Received: by filter1458p1mdw1.sendgrid.net with SMTP id filter1458p1mdw1-10777-5BFCB0E4-6 2018-11-27 02:50:12.376051645 +0000 UTC m=+2929.732093868
Received: from github-lowworker-3c598a3.cp1-iad.github.net (unknown [192.30.252.43]) by ismtpd0019p1iad1.sendgrid.net (SG) with ESMTP id FgUHbkTpQGSoNn2ODtUKAA for <quic-issues@ietf.org>; Tue, 27 Nov 2018 02:50:12.336 +0000 (UTC)
Received: from github.com (localhost [127.0.0.1]) by github-lowworker-3c598a3.cp1-iad.github.net (Postfix) with ESMTP id 4FA17A802A4 for <quic-issues@ietf.org>; Mon, 26 Nov 2018 18:50:12 -0800 (PST)
Date: Tue, 27 Nov 2018 02:50:12 +0000
From: martinduke <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+0166e4ab11cf022c3bd207cff5be49fa102532e367e0c22192cf00000001181472e492a169ce16b355af@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/c441878674@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_5bfcb0e44cd77_35f43fb33bad45c05271a"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: martinduke
X-GitHub-Recipient: quic-issues
X-GitHub-Reason: subscribed
X-Auto-Response-Suppress: All
X-GitHub-Recipient-Address: quic-issues@ietf.org
X-SG-EID: l64QuQ2uJCcEyUykJbxN122A6QRmEpucztpreh3Pak3FcqVIIPLK3WxyrlErEy2UQY4TSUKclsWJEO 7bHknbChEYCtYb5MyBCSMgs8as6VhzIcIDTzBOz0e6FarBPGNGSk+jFyF00Yn2kDXev5E5JdLRX8cf /XY9m7OUfJ4vKvCtATYPWhMZI20QwhP836uy3sq0Uc2Hslv9Wl6Vl2ycEQEj+CJLKHIYHrenvc0aXZ g=
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic-issues/opotJztGEr7S6y4n-VsGmoBMHME>
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, 27 Nov 2018 02:50:16 -0000

Alright, how about this:

"Senders use a FIN to indicate the end of an HTTP request or response. Absent a CONNECT method in the request, senders MUST NOT make the sending of FIN dependent on receipt of a response from the peer.

However, due to the possible presence of a CONNECT method, and the opportunity to send HTTP_EARLY_DATA, servers SHOULD begin processing partial HTTP messages once enough of the message has been received to make progress. If a client stream terminates without enough of the HTTP message to provide a complete response, the server SHOULD abort its response with the error code HTTP_INCOMPLETE_REQUEST."

I'm open to making the server requirement a similar MUST -- "servers MUST NOT be dependent on a FIN to start processing..." if people think that would help avoid CONNECT deadlocks.

-- 
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-441878674

v2.23.0 | Report a Bug | By Email