Re: [httpapi] draft-ietf-httpapi-deprecation-header and the status code

Erik Wilde <erik.wilde@dret.net> Tue, 09 November 2021 15:44 UTC

Return-Path: <erik.wilde@dret.net>
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 07A453A0817 for <httpapi@ietfa.amsl.com>; Tue, 9 Nov 2021 07:44:43 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.227
X-Spam-Level:
X-Spam-Status: No, score=-5.227 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, NICE_REPLY_A=-3.33, SPF_HELO_NONE=0.001, SPF_NONE=0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
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 lotiiYBzaSIE for <httpapi@ietfa.amsl.com>; Tue, 9 Nov 2021 07:44:38 -0800 (PST)
Received: from mxout017.mail.hostpoint.ch (mxout017.mail.hostpoint.ch [IPv6:2a00:d70:0:e::317]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7A0123A07B1 for <httpapi@ietf.org>; Tue, 9 Nov 2021 07:44:37 -0800 (PST)
Received: from [10.0.2.46] (helo=asmtp013.mail.hostpoint.ch) by mxout017.mail.hostpoint.ch with esmtp (Exim 4.94.2 (FreeBSD)) (envelope-from <erik.wilde@dret.net>) id 1mkTIV-0002Qf-AY; Tue, 09 Nov 2021 16:44:31 +0100
Received: from ip5b41ddc0.dynamic.kabel-deutschland.de ([91.65.221.192] helo=[192.168.178.42]) by asmtp013.mail.hostpoint.ch with esmtpa (Exim 4.94.2 (FreeBSD)) (envelope-from <erik.wilde@dret.net>) id 1mkTIV-000Ggq-79; Tue, 09 Nov 2021 16:44:31 +0100
X-Authenticated-Sender-Id: erik.wilde@dret.net
To: Stephane Bortzmeyer <bortzmeyer@nic.fr>, httpapi@ietf.org
References: <YYqO8Ya2PU5GetjH@nic.fr>
From: Erik Wilde <erik.wilde@dret.net>
Message-ID: <2ba2af3d-26f5-80fa-0ef8-bd552c75c47c@dret.net>
Date: Tue, 09 Nov 2021 16:44:30 +0100
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:78.0) Gecko/20100101 Thunderbird/78.14.0
MIME-Version: 1.0
In-Reply-To: <YYqO8Ya2PU5GetjH@nic.fr>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/httpapi/1e-gFi-i4UNGqnIcY3mmOa8dvpI>
Subject: Re: [httpapi] draft-ietf-httpapi-deprecation-header and the status code
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: Tue, 09 Nov 2021 15:44:43 -0000

hello stephane.

On 2021-11-09 16:08, Stephane Bortzmeyer wrote:
> I do not find a mention of the HTTP status code to use then adding the
> deprecation header. Does it mean it can be used with 200, 404, 410?

it can (we're not disallowing it), but it probably doesn't make a lot of 
sense to use it on 4xx or 5xx codes, since these indicate a problem that 
has to be resolved. that means that nothing keeps you from using the 
header field with error messages, but it's unlikely that this would be 
very useful.

cheers,

dret.

-- 
erik wilde | mailto:erik.wilde@dret.net |
            | http://dret.net/netdret    |
            | http://twitter.com/dret    |