IETF Logo Mail Archive

Re: [httpapi] client-specified timeout?

James <james.ietf@gmail.com> Fri, 05 February 2021 19:04 UTC

Return-Path: <james.ietf@gmail.com>
X-Original-To: httpapi@ietfa.amsl.com
Delivered-To: httpapi@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DD2D33A0E82 for <httpapi@ietfa.amsl.com>; Fri, 5 Feb 2021 11:04:10 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.098
X-Spam-Level:
X-Spam-Status: No, score=-2.098 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.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 EJYJAxiF2Zjz for <httpapi@ietfa.amsl.com>; Fri, 5 Feb 2021 11:04:08 -0800 (PST)
Received: from mail-il1-x130.google.com (mail-il1-x130.google.com [IPv6:2607:f8b0:4864:20::130]) (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 999493A0E7E for <httpapi@ietf.org>; Fri, 5 Feb 2021 11:04:08 -0800 (PST)
Received: by mail-il1-x130.google.com with SMTP id q9so6816014ilo.1 for <httpapi@ietf.org>; Fri, 05 Feb 2021 11:04:08 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc:content-transfer-encoding; bh=tDxM58qrB9pi4qwDtG1H4XYtmKQnjzB8n1kVxZBci7E=; b=eHVNbo5ckZF+cnloW8Nrc6oUkqmJw51Cmnm8NzAx6gLQOMH4jIIYdE/rXUX8NexhdP D3zif2xeCz1+aZsrxP8U890YYmIBZzB0TxX2oScpMK4DbdYj8PufexSDqz9WcaYfxZVb peM0LZqnxv8HR5b0aZKSdBXD08elc0Ds2CL21wv6yLVURF69IYpSHc9Ei9pAHTuwjSMM olK1ckgmWrACY//5Z0U/hCPBhsdgjJM9w2EmWDyXhYWRRG01x4BcIV98Z1ev552WEfPO mvewzTYXqfC8Ba5gxk9Rp1q9eb+tQniA2IkWcUW5Ln51E0QSwLGCz3J6NJRusBV3yD5+ rkkg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc:content-transfer-encoding; bh=tDxM58qrB9pi4qwDtG1H4XYtmKQnjzB8n1kVxZBci7E=; b=FmmhjJlxrcAn8Y7/ZgitE43vGoZfHTkIvcbp0oBNuZKcsyacHUYhwo49DBpahVLJGv j1V5BGdAeO5itJ0T6qpdHr9SRe0pi+Z3fpNti0zeRti1yyjIj8g1NNY60U5PM2VHjdyp V2bLh9Q6oads3vrFqVeCElgY6k/yS+6aWt3yOUB8UNp7PL/01475baph3dZqTM4JtbIl PjoLImeiwx+vZTYA8316jLxlGzxm7+phiN1N+1lCpTgIPd3+Dj3Fvt33zJV2huNt85aX VLMXfXo+gvXqRVWe7gAkpQJ0km/FBw8SBVtC9dPC/ufN1FFZYLG79fDj7VVv12YTh3Mx fLAQ==
X-Gm-Message-State: AOAM533uxQ/VPIK8z7TnzpDoahQZgHXxz3RwUx7GWpo+zc3y5aGax7Y+ idsYO1sygnoog26ysePNHF7CS/d879EtWs3w+qY=
X-Google-Smtp-Source: ABdhPJwBfeXLW0rYJVFlNwmj3AWjyW23hPMs662vLFg7a7vSKUC6QFPaRTxbpB2djLzlhHLIKs2nDrGWwc71aZwWWMs=
X-Received: by 2002:a05:6e02:1608:: with SMTP id t8mr5140866ilu.79.1612551847907; Fri, 05 Feb 2021 11:04:07 -0800 (PST)
MIME-Version: 1.0
References: <7613F010-431C-47B3-802E-5258BAA5E156@akamai.com>
In-Reply-To: <7613F010-431C-47B3-802E-5258BAA5E156@akamai.com>
From: James <james.ietf@gmail.com>
Date: Fri, 05 Feb 2021 20:03:56 +0100
Message-ID: <CAO+dDxmHSDX1=ouEqNJMX-=Z4ygWysEciWq=QygVm_kF_58OFQ@mail.gmail.com>
To: "Salz, Rich" <rsalz=40akamai.com@dmarc.ietf.org>
Cc: "httpapi@ietf.org" <httpapi@ietf.org>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/httpapi/6nndz5i1f14XnQERdPkl2vu0zTM>
Subject: Re: [httpapi] client-specified timeout?
X-BeenThere: httpapi@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Building Blocks for HTTP APIs <httpapi.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/httpapi>, <mailto:httpapi-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/httpapi/>
List-Post: <mailto:httpapi@ietf.org>
List-Help: <mailto:httpapi-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/httpapi>, <mailto:httpapi-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 05 Feb 2021 19:04:11 -0000

If your ask is about standardisation of the request header and
negotiation of it, yes I would be interested. But my biggest question
is about how the server should respond - 504 assumes the server is a
proxy, 408 is for unused connections, neither of these at initial
glance appear to fit the use case.

- J

On Fri, 5 Feb 2021 at 19:54, Salz, Rich
<rsalz=40akamai.com@dmarc.ietf.org> wrote:
>
> Is it reasonable for a client to want the ability to say things like “if this takes more than 300ms send a failure status code back” ?
>
> Anyone in the WG interested in thinking/working on this?
>
>
>
> --
> httpapi mailing list
> httpapi@ietf.org
> https://www.ietf.org/mailman/listinfo/httpapi

v2.23.0 | Report a Bug | By Email