IETF Logo Mail Archive

[quicwg/base-drafts] HTTP/3 Client handling of SERVER_BUSY error code needs to be specified (#2699)

Praveen Balasubramanian <notifications@github.com> Tue, 14 May 2019 21:52 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 0BCD61200E6 for <quic-issues@ietfa.amsl.com>; Tue, 14 May 2019 14:52:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.465
X-Spam-Level:
X-Spam-Status: No, score=-6.465 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_IMAGE_ONLY_20=1.546, HTML_MESSAGE=0.001, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H2=-0.001, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01] 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 96gHZSmK0AWz for <quic-issues@ietfa.amsl.com>; Tue, 14 May 2019 14:52:00 -0700 (PDT)
Received: from out-5.smtp.github.com (out-5.smtp.github.com [192.30.252.196]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9CFEF12003F for <quic-issues@ietf.org>; Tue, 14 May 2019 14:52:00 -0700 (PDT)
Date: Tue, 14 May 2019 14:51:59 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1557870719; bh=VmzA/YgSWSNDd29zY74sYFYVasrXhRNq6BdlG5D4xn4=; h=Date:From:Reply-To:To:Cc:Subject:List-ID:List-Archive:List-Post: List-Unsubscribe:From; b=O9tGRudrEPGooTABZ4H77Z8G9t/PDaoXQ01EMvc4cwxlDr4vanrNiM0vUXcTxdWkx RxP9ndNE0FqPHxq+9Cbh1k7IqzAX+xk9NXeCrpuTKGnaYU+ctsyFKApTtMsjJWH/Pz 555b6EN99lmkRf06JvwaUgaLrIBHOeLwEdaBqPHg=
From: Praveen Balasubramanian <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+AFTOJKY2JDYWN6UK6ZLJC4V25BVP7EVBNHHBU6IQGY@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/issues/2699@github.com>
Subject: [quicwg/base-drafts] HTTP/3 Client handling of SERVER_BUSY error code needs to be specified (#2699)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5cdb387fbc3d8_5b9f3fcb9e2cd96471614d"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: pravb
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/N-sC89odsBdhMpNLaFq51w5vljo>
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, 14 May 2019 21:52:02 -0000

The transport draft defines the SERVER_BUSY error code. It is suggested that this error code be sent when the server cannot process new connections for example when it is under DoS attack or wants to take down the QUIC endpoint for servicing. The HTTP/3 draft should specify how a client should handle this error. IMO the client in this case should fallback to HTTP/2. 

-- 
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/2699

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