[quicwg/base-drafts] What indicates the end of a message? (#2230)

ekr <notifications@github.com> Thu, 20 December 2018 23:10 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 []) by ietfa.amsl.com (Postfix) with ESMTP id 917D9131257 for <quic-issues@ietfa.amsl.com>; Thu, 20 Dec 2018 15:10:34 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.661
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 ([]) by localhost (ietfa.amsl.com []) (amavisd-new, port 10024) with ESMTP id YSM35PeO686l for <quic-issues@ietfa.amsl.com>; Thu, 20 Dec 2018 15:10:32 -0800 (PST)
Received: from out-2.smtp.github.com (out-2.smtp.github.com []) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 16C7F130F21 for <quic-issues@ietf.org>; Thu, 20 Dec 2018 15:10:32 -0800 (PST)
Date: Thu, 20 Dec 2018 15:10:30 -0800
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1545347430; bh=UHb+LPhLfQRpZ1faKm3VT0p66yuQMQn+er6AtM5e8Bk=; h=Date:From:Reply-To:To:Cc:Subject:List-ID:List-Archive:List-Post: List-Unsubscribe:From; b=Yfcw2zIPzMq10lFrUxAmOOyaif1g2ZmXqF9o9BijtelkeCXWz3nm+3M8toIKvG8JV hF10u3k56hF5DRmoTJTUOZfKvf2QVK74s7sD+GgN0cc5PM1qCfm+krCsTWOKLbNyKG delijdN2m38o60JzCVpkmNh3eKPk7MY+BMJJHARE=
From: ekr <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+0166e4ab48abaf835bba0f336c50402b4a3afdd6f4525d5e92cf000000011833e36692a169ce17707462@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/issues/2230@github.com>
Subject: [quicwg/base-drafts] What indicates the end of a message? (#2230)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5c1c2166423df_25893fe4d5cd45c0706da"; 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/4Fhi1HDkB6h0gI-7AC0UE_Mowqk>
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:10:34 -0000

S 5.

When a stream is closed, this indicates the end of an HTTP message. Because some
messages are large or unbounded, endpoints 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

This creates two ways to say the end of the HTTP messages:

- Send the HEADERs frame (at which point you have to close,
  but you know its done)
- Don't send the HEADERs frame and close the stream

That seems a bit unfortunate. Would it make more sense to require the final HEADERS frame, even if it were empty?

Also, can the server send PUSH_PROMISE after the second HEADERS. I think no, but...

You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub: