IETF Logo Mail Archive

[Editorial Errata Reported] RFC9110 (7530)

RFC Errata System <rfc-editor@rfc-editor.org> Mon, 29 May 2023 21:49 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 0C19FC14F748 for <ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com>; Mon, 29 May 2023 14:49:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.946
X-Spam-Level:
X-Spam-Status: No, score=-4.946 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.25, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H5=0.001, RCVD_IN_MSPIKE_WL=0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_PASS=-0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=unavailable 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 nqSwI4eG5LJS for <ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com>; Mon, 29 May 2023 14:49:51 -0700 (PDT)
Received: from lyra.w3.org (lyra.w3.org [128.30.52.18]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange ECDHE (P-256) server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5094AC1516E2 for <httpbisa-archive-bis2Juki@lists.ietf.org>; Mon, 29 May 2023 14:49:51 -0700 (PDT)
Received: from lists by lyra.w3.org with local (Exim 4.94.2) (envelope-from <ietf-http-wg-request@listhub.w3.org>) id 1q3khs-00Fzci-O3 for ietf-http-wg-dist@listhub.w3.org; Mon, 29 May 2023 21:47:12 +0000
Resent-Date: Mon, 29 May 2023 21:47:12 +0000
Resent-Message-Id: <E1q3khs-00Fzci-O3@lyra.w3.org>
Received: from mimas.w3.org ([128.30.52.79]) by lyra.w3.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from <wwwrun@rfcpa.amsl.com>) id 1q3khq-00FzbF-FJ for ietf-http-wg@listhub.w3.org; Mon, 29 May 2023 21:47:10 +0000
Received: from rfc-editor.org ([50.223.129.200] helo=rfcpa.amsl.com) by mimas.w3.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from <wwwrun@rfcpa.amsl.com>) id 1q3khq-003sNs-DT for ietf-http-wg@w3.org; Mon, 29 May 2023 21:47:10 +0000
Received: by rfcpa.amsl.com (Postfix, from userid 499) id 0DAA385293; Mon, 29 May 2023 14:47:03 -0700 (PDT)
To: rfc-editor@rfc-editor.org
From: RFC Errata System <rfc-editor@rfc-editor.org>
Cc: chealer@gmail.com, fielding@gbiv.com, mnot@mnot.net, julian.reschke@greenbytes.de, ietf-http-wg@w3.org
Content-Type: text/plain; charset="UTF-8"
Message-Id: <20230529214703.0DAA385293@rfcpa.amsl.com>
Date: Mon, 29 May 2023 14:47:03 -0700
Received-SPF: pass client-ip=50.223.129.200; envelope-from=wwwrun@rfcpa.amsl.com; helo=rfcpa.amsl.com
X-W3C-Hub-Spam-Status: No, score=-7.0
X-W3C-Hub-Spam-Report: BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.25, RCVD_IN_DNSWL_MED=-2.3, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, W3C_AA=-1, W3C_IRA=-1, W3C_WL=-1
X-W3C-Scan-Sig: mimas.w3.org 1q3khq-003sNs-DT ffc1bf85be08ec77197076bc044f7094
X-Original-To: ietf-http-wg@w3.org
Subject: [Editorial Errata Reported] RFC9110 (7530)
Archived-At: <https://www.w3.org/mid/20230529214703.0DAA385293@rfcpa.amsl.com>
Resent-From: ietf-http-wg@w3.org
X-Mailing-List: <ietf-http-wg@w3.org> archive/latest/51124
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: <https://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 submitted for RFC9110,
"HTTP Semantics".

--------------------------------------
You may review the report below and at:
https://www.rfc-editor.org/errata/eid7530

--------------------------------------
Type: Editorial
Reported by: Philippe Cloutier <chealer@gmail.com>

Section: 15.5.2.

Original Text
-------------
The 401 (Unauthorized) status code indicates that the request has not
been applied because it lacks valid authentication credentials for
the target resource.

Corrected Text
--------------
The 401 (Unauthorized) status code indicates that the request has not
been processed because it lacks valid authentication credentials for
the target resource.

Notes
-----
"applying a request" is not a standard expression. Usually, requests are "treated", "granted" or "processed".

This phrasing was imported in Apache Tomcat; thanks to Mark Thomas for pointing out it came from this RFC.

Instructions:
-------------
This erratum is currently posted as "Reported". If necessary, please
use "Reply All" to discuss whether it should be verified or
rejected. When a decision is reached, the verifying party  
can log in to change the status and edit the report, if necessary. 

--------------------------------------
RFC9110 (draft-ietf-httpbis-semantics-19)
--------------------------------------
Title               : HTTP Semantics
Publication Date    : June 2022
Author(s)           : R. Fielding, Ed., M. Nottingham, Ed., J. Reschke, Ed.
Category            : INTERNET STANDARD
Source              : HTTP
Area                : Applications and Real-Time
Stream              : IETF
Verifying Party     : IESG

v2.23.0 | Report a Bug | By Email