[Errata Held for Document Update] RFC7540 (4666)
RFC Errata System <rfc-editor@rfc-editor.org> Thu, 23 February 2017 15:08 UTC
Return-Path: <ietf-http-wg-request+bounce-httpbisa-archive-bis2juki=lists.ie@listhub.w3.org>
X-Original-To: ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com
Delivered-To: ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 22854129980 for <ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com>; Thu, 23 Feb 2017 07:08:33 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.901
X-Spam-Level:
X-Spam-Status: No, score=-6.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.001, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=unavailable 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 CnDqBc0WZegD for <ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com>; Thu, 23 Feb 2017 07:08:32 -0800 (PST)
Received: from frink.w3.org (frink.w3.org [128.30.52.56]) (using TLSv1.2 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0FF21129979 for <httpbisa-archive-bis2Juki@lists.ietf.org>; Thu, 23 Feb 2017 07:08:32 -0800 (PST)
Received: from lists by frink.w3.org with local (Exim 4.80) (envelope-from <ietf-http-wg-request@listhub.w3.org>) id 1cguyX-0005u8-Sq for ietf-http-wg-dist@listhub.w3.org; Thu, 23 Feb 2017 15:06:33 +0000
Resent-Date: Thu, 23 Feb 2017 15:06:33 +0000
Resent-Message-Id: <E1cguyX-0005u8-Sq@frink.w3.org>
Received: from titan.w3.org ([128.30.52.76]) by frink.w3.org with esmtps (TLS1.2:RSA_AES_128_CBC_SHA1:128) (Exim 4.80) (envelope-from <wwwrun@rfc-editor.org>) id 1cguyN-0005je-OK for ietf-http-wg@listhub.w3.org; Thu, 23 Feb 2017 15:06:23 +0000
Received: from rfc-editor.org ([4.31.198.49]) by titan.w3.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.84_2) (envelope-from <wwwrun@rfc-editor.org>) id 1cguyF-0007m1-CA for ietf-http-wg@w3.org; Thu, 23 Feb 2017 15:06:18 +0000
Received: by rfc-editor.org (Postfix, from userid 30) id 696B1B81702; Thu, 23 Feb 2017 07:05:22 -0800 (PST)
To: vfaronov@gmail.com, mike@belshe.com, fenix@google.com, martin.thomson@gmail.com
X-PHP-Originating-Script: 30:errata_mail_lib.php
From: RFC Errata System <rfc-editor@rfc-editor.org>
Cc: aamelnikov@fastmail.fm, iesg@ietf.org, ietf-http-wg@w3.org, rfc-editor@rfc-editor.org, charset=UTF-8@rfc-editor.org
Message-Id: <20170223150522.696B1B81702@rfc-editor.org>
Date: Thu, 23 Feb 2017 07:05:22 -0800
Received-SPF: pass client-ip=4.31.198.49; envelope-from=wwwrun@rfc-editor.org; helo=rfc-editor.org
X-W3C-Hub-Spam-Status: No, score=-8.2
X-W3C-Hub-Spam-Report: AWL=2.008, BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, W3C_AA=-1, W3C_IRA=-1, W3C_IRR=-3, W3C_WL=-1
X-W3C-Scan-Sig: titan.w3.org 1cguyF-0007m1-CA 3e15dc22729ede4c69d8eee8ad89b4b7
X-Original-To: ietf-http-wg@w3.org
Subject: [Errata Held for Document Update] RFC7540 (4666)
Archived-At: <http://www.w3.org/mid/20170223150522.696B1B81702@rfc-editor.org>
Resent-From: ietf-http-wg@w3.org
X-Mailing-List: <ietf-http-wg@w3.org> archive/latest/33598
X-Loop: ietf-http-wg@w3.org
Resent-Sender: ietf-http-wg-request@w3.org
Precedence: list
List-Id: <ietf-http-wg.w3.org>
List-Help: <http://www.w3.org/Mail/>
List-Post: <mailto:ietf-http-wg@w3.org>
List-Unsubscribe: <mailto:ietf-http-wg-request@w3.org?subject=unsubscribe>
The following errata report has been held for document update for RFC7540, "Hypertext Transfer Protocol Version 2 (HTTP/2)". -------------------------------------- You may review the report below and at: http://www.rfc-editor.org/errata_search.php?rfc=7540&eid=4666 -------------------------------------- Status: Held for Document Update Type: Technical Reported by: Vasiliy Faronov <vfaronov@gmail.com> Date Reported: 2016-04-13 Held by: Alexey Melnikov (IESG) Section: 9.1.2 Original Text ------------- A 421 response is cacheable by default, i.e., unless otherwise indicated by the method definition or explicit cache controls (see Section 4.2.2 of [RFC7234]). Corrected Text -------------- [paragraph removed] Notes ----- The HTTP cache key (RFC 7234 Section 2) is based on the request URI, not on properties of the connection. Therefore, if a client were to cache a 421 response, it would then use this cached 421 to satisfy further requests to the same URI, before it has a chance to connect to an authoritative server. Mark Nottingham: As discussed on list, I think the best we can do here is to note that in many cases, it'd be desireable to mark this as explicitly uncacheable. With this paragraph removed, a 421 response is not cacheable by default, per RFC 7231 Section 6.1. -------------------------------------- RFC7540 (draft-ietf-httpbis-http2-17) -------------------------------------- Title : Hypertext Transfer Protocol Version 2 (HTTP/2) Publication Date : May 2015 Author(s) : M. Belshe, R. Peon, M. Thomson, Ed. Category : PROPOSED STANDARD Source : Hypertext Transfer Protocol Bis APP Area : Applications Stream : IETF Verifying Party : IESG
- [Errata Held for Document Update] RFC7540 (4666) RFC Errata System