IETF Logo Mail Archive

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

Lucas Pardue <notifications@github.com> Wed, 15 May 2019 17:44 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 C2FC2120422 for <quic-issues@ietfa.amsl.com>; Wed, 15 May 2019 10:44:35 -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 kHYGUPxKWK2U for <quic-issues@ietfa.amsl.com>; Wed, 15 May 2019 10:44:34 -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 A1E531203F1 for <quic-issues@ietf.org>; Wed, 15 May 2019 10:44:32 -0700 (PDT)
Date: Wed, 15 May 2019 10:44:31 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1557942271; bh=xFX+2e+hYnlM7ZGeAXBJAmaBYJcLhxbQv6zw2L/WIN4=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=jbFq4iI5MaP5rcTH17lHUR33HYHN+1Ghx1060heFkFSYVfJ2Ebd36EUiXBDM8Zqpk MhCxoDyOvv3rvus0BN/Hv5QQM/RcdCcaMj6iJLimox/+5Ps5YLkCF6wIkxSewlnENw Bk8vheQ7/I81rFqj89s85+EURALRPoK99WTUQswE=
From: Lucas Pardue <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+AFTOJKYXRFX2KWQ223O5QU525GBH7EVBNHHBU6IQGY@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/492754041@github.com>
In-Reply-To: <quicwg/base-drafts/issues/2699@github.com>
References: <quicwg/base-drafts/issues/2699@github.com>
Subject: Re: [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_5cdc4fff7496e_13703fd64e8cd96c7335a7"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: LPardue
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/KZUCXmRlbg93yzZn831HL9MeQbw>
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: Wed, 15 May 2019 17:44:40 -0000

I believe Chrome have some behaviour like that. It isn't codified into the specs but I'm sure there is some good practice out there we can learn from.

For instance, fallback from a HTTP level error (I.e. a 500) was discussed on the HTTPbis mailing list in the last year.

-- 
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#issuecomment-492754041

v2.23.0 | Report a Bug | By Email