- From: RFC Errata System <rfc-editor@rfc-editor.org>
- Date: Fri, 7 Jul 2023 14:22:39 -0700 (PDT)
- To: chealer@gmail.com, fielding@gbiv.com, mnot@mnot.net, julian.reschke@greenbytes.de
- Cc: rfc-ed@rfc-editor.org, iesg@ietf.org, ietf-http-wg@w3.org
The following errata report has been rejected for RFC9110, "HTTP Semantics". -------------------------------------- You may review the report below and at: https://www.rfc-editor.org/errata/eid7530 -------------------------------------- Status: Rejected Type: Editorial Reported by: Philippe Cloutier <chealer@gmail.com> Date Reported: 2023-05-29 Rejected by: RFC Editor 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. --VERIFIER NOTES-- A method is applied to a resource to have an effect that results in a response. Any web search on "method applied" will show you that it is quite common in standard English. The request has already been processed, at least partially, in order to make a decision that resulted in a 401 error -------------------------------------- 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
Received on Friday, 7 July 2023 21:22:45 UTC