[rfc-dist] RFC 9211 on The Cache-Status HTTP Response Header Field
rfc-editor@rfc-editor.org Wed, 08 June 2022 18:53 UTC
Return-Path: <rfc-dist-bounces@rfc-editor.org>
X-Original-To: ietfarch-rfc-dist-archive@ietfa.amsl.com
Delivered-To: ietfarch-rfc-dist-archive@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id E4E98C0555BC; Wed, 8 Jun 2022 11:53:57 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=ietf.org; s=ietf1; t=1654714438; bh=n3AgEYX7pFVn7DNltTBcrJ9/0NKtHHS/LzIn0gVE0lY=; h=To:From:Cc:Date:Subject:List-Id:List-Unsubscribe:List-Archive: List-Post:List-Help:List-Subscribe; b=eovA4gUWCF7k46gKhZfL97RFaduQ0MZnqIiEKO1oPOOfqGj0KH6mgwVVoSkoxJneV ksKUZw7FuzxdJyhQfxYEIfFMdI+Dt0mlSSmJhHfFj8R6lYMeMgFYL860qlragAXR2i Y6CTp0je/B7fqBqBsjyb6LkQ3GED52Nebxqknxs8=
X-Mailbox-Line: From rfc-dist-bounces@rfc-editor.org Wed Jun 8 11:53:57 2022
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 8FB53C0795B4; Wed, 8 Jun 2022 11:53:56 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=ietf.org; s=ietf1; t=1654714436; bh=n3AgEYX7pFVn7DNltTBcrJ9/0NKtHHS/LzIn0gVE0lY=; h=To:From:Cc:Date:Subject:List-Id:List-Unsubscribe:List-Archive: List-Post:List-Help:List-Subscribe; b=M4c75ABO4AHLiWYxEJa+W67DKOlH6xYlI+CQvkzZetejXF7Njh1FaKTRvBB8A6GLb Ia+GEiL9sek3DbxI/zytrTZn9DvEOD+NGwVCXkMD9seCpBqMDPHn6piAa98+HT7+3a wU3l2zksYXL6boh7Us5B1NIVB8CBUi+sFlB/ISMM=
X-Original-To: rfc-dist@ietfa.amsl.com
Delivered-To: rfc-dist@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A051BC1A7F9F; Wed, 8 Jun 2022 11:53:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.656
X-Spam-Level:
X-Spam-Status: No, score=-1.656 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.25, RCVD_IN_DNSWL_BLOCKED=0.001, SPF_HELO_NONE=0.001, SPF_NONE=0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 70aVSbutaeC6; Wed, 8 Jun 2022 11:53:50 -0700 (PDT)
Received: from rfcpa.amsl.com (rfc-editor.org [50.223.129.200]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id F3AD8C15791C; Wed, 8 Jun 2022 11:53:49 -0700 (PDT)
Received: by rfcpa.amsl.com (Postfix, from userid 499) id BD440CF503; Wed, 8 Jun 2022 11:53:48 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
From: rfc-editor@rfc-editor.org
Cc: rfc-editor@rfc-editor.org, drafts-update-ref@iana.org, ietf-http-wg@w3.org
Message-Id: <20220608185348.BD440CF503@rfcpa.amsl.com>
Date: Wed, 08 Jun 2022 11:53:48 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/rfc-dist/4TMTnE3Ay0CVQUKa9vh3cYoMGJ0>
Subject: [rfc-dist] RFC 9211 on The Cache-Status HTTP Response Header Field
X-BeenThere: rfc-dist@rfc-editor.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: RFC Announcements <rfc-dist.rfc-editor.org>
List-Unsubscribe: <https://mailman.rfc-editor.org/mailman/options/rfc-dist>, <mailto:rfc-dist-request@rfc-editor.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/rfc-dist/>
List-Post: <mailto:rfc-dist@rfc-editor.org>
List-Help: <mailto:rfc-dist-request@rfc-editor.org?subject=help>
List-Subscribe: <https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist>, <mailto:rfc-dist-request@rfc-editor.org?subject=subscribe>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Errors-To: rfc-dist-bounces@rfc-editor.org
Sender: rfc-dist <rfc-dist-bounces@rfc-editor.org>
A new Request for Comments is now available in online RFC libraries.
RFC 9211
Title: The Cache-Status HTTP Response Header Field
Author: M. Nottingham
Status: Standards Track
Stream: IETF
Date: June 2022
Mailbox: mnot@mnot.net
Pages: 9
Updates/Obsoletes/SeeAlso: None
I-D Tag: draft-ietf-httpbis-cache-header-10.txt
URL: https://www.rfc-editor.org/info/rfc9211
DOI: 10.17487/RFC9211
To aid debugging, HTTP caches often append header fields to a
response, explaining how they handled the request in an ad hoc
manner. This specification defines a standard mechanism to do so that
is aligned with HTTP's caching model.
This document is a product of the HTTP Working Group of the IETF.
This is now a Proposed Standard.
STANDARDS TRACK: This document specifies an Internet Standards Track
protocol for the Internet community, and requests discussion and suggestions
for improvements. Please refer to the current edition of the Official
Internet Protocol Standards (https://www.rfc-editor.org/standards) for the
standardization state and status of this protocol. Distribution of this
memo is unlimited.
This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
https://www.ietf.org/mailman/listinfo/ietf-announce
https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist
For searching the RFC series, see https://www.rfc-editor.org/search
For downloading RFCs, see https://www.rfc-editor.org/retrieve/bulk
Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor@rfc-editor.org. Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.
The RFC Editor Team
Association Management Solutions, LLC
_______________________________________________
rfc-dist mailing list
rfc-dist@rfc-editor.org
https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist
http://www.rfc-editor.org