- From: RFC Errata System <rfc-editor@rfc-editor.org>
- Date: Mon, 23 Oct 2023 02:42:33 -0700 (PDT)
- To: daveshawley@gmail.com, fielding@gbiv.com, mnot@mnot.net, julian.reschke@greenbytes.de
- Cc: francesca.palombini@ericsson.com, iesg@ietf.org, ietf-http-wg@w3.org, iana@iana.org, rfc-editor@rfc-editor.org
The following errata report has been verified for RFC9110, "HTTP Semantics". -------------------------------------- You may review the report below and at: https://www.rfc-editor.org/errata/eid7419 -------------------------------------- Status: Verified Type: Technical Reported by: Dave Shawley <daveshawley@gmail.com> Date Reported: 2023-04-11 Verified by: Francesca Palombini (IESG) Section: 8.3.2 Original Text ------------- In the fields defined by this document, charset names appear either in parameters (Content-Type), or, for Accept-Encoding, in the form of a plain token. Corrected Text -------------- In the fields defined by this document, charset names appear either in parameters (Content-Type), or, for Accept-Charset, in the form of a plain token. Notes ----- Accept-Encoding is the preferred list of response content codings. Accept-Charset is the preferred list of response charsets. -------------------------------------- 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
Received on Monday, 23 October 2023 09:42:39 UTC