IETF Logo Mail Archive

Re: [quicwg/base-drafts] http deadlock with stream FIN choices (#1972)

Ryan Hamilton <notifications@github.com> Tue, 06 November 2018 15:14 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 9959F130DFE for <quic-issues@ietfa.amsl.com>; Tue, 6 Nov 2018 07:14:54 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -8.47
X-Spam-Level:
X-Spam-Status: No, score=-8.47 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.47, 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 KFgCT_TwDF7W for <quic-issues@ietfa.amsl.com>; Tue, 6 Nov 2018 07:14:53 -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 F40E012F1A2 for <quic-issues@ietf.org>; Tue, 6 Nov 2018 07:14:52 -0800 (PST)
Date: Tue, 06 Nov 2018 07:14:51 -0800
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1541517291; bh=BjN8J8dU9yi0Eos220Huh31ro4F+7nzDWhZEHHyx57I=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=egX+9FmFInP8BCkZnm6Loj3dk4458SYMJJ8+AWxxCXyfshdsnERellVOibrdf5/D/ KXrQJvVIObkSygBQQ7ah2Z5OMXi2WxivE6bez93/1xg/V2hacS+XNl/luhz5MO5kJN EhTWLhH33Wt7lF0Aq3kBcNXKJoflEN9nO1Ixaw0s=
From: Ryan Hamilton <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+0166e4ab90cf35dc879e5c70b9440288480731bdb33960ca92cf0000000117f971eb92a169ce1683c825@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/issues/1972/436287934@github.com>
In-Reply-To: <quicwg/base-drafts/issues/1972@github.com>
References: <quicwg/base-drafts/issues/1972@github.com>
Subject: Re: [quicwg/base-drafts] http deadlock with stream FIN choices (#1972)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5be1afebac325_bd73ff384cd45bc5355a"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: RyanAtGoogle
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/95CFkJd6CsRMVB997IQZSRYDVjU>
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, 06 Nov 2018 15:14:54 -0000

It seems quite reasonable for servers to wait for the FIN before sending
the response. As such it seems like requiring the client FIN the request to
avoid deadlock makes sense to me.

On Tue, Nov 6, 2018 at 1:20 AM, Kazuho Oku <notifications@github.com> wrote:

> I agree with @nibanks <https://github.com/nibanks>.
>
> HTTP/0.9 has two ways of terminating a request: CRLF and a FIN. HTTP/1
> introduced the concept of request body along with a content-length
> request header field that allows a server to detect the end of the request
> *without* using FIN.
>
> It is not the case with H2, where END_STREAM is the only way to terminate
> a request. I'd assume that that is the same with H3.
>
> —
> You are receiving this because you are subscribed to this thread.
> Reply to this email directly, view it on GitHub
> <https://github.com/quicwg/base-drafts/issues/1972#issuecomment-436184007>,
> or mute the thread
> <https://github.com/notifications/unsubscribe-auth/ASp6ymtvyKrIGgQV76RCqI8uVeoFAbuAks5usVRPgaJpZM4YP8rZ>
> .
>


-- 
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/1972#issuecomment-436287934

v2.34.0 | Report a Bug | By Email | System Status