- From: RFC Errata System <rfc-editor@rfc-editor.org>
- Date: Fri, 11 Aug 2023 10:52:17 -0700 (PDT)
- To: fielding@gbiv.com, mnot@mnot.net, julian.reschke@greenbytes.de, superuser@gmail.com, francesca.palombini@ericsson.com, mnot@mnot.net, tpauly@apple.com
- Cc: justine@justinekrejcha.com, ietf-http-wg@w3.org, rfc-editor@rfc-editor.org
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/eid7599 -------------------------------------- Type: Technical Reported by: Justine Krejcha <justine@justinekrejcha.com> Section: 6.4.1 Original Text ------------- All 1xx (Informational), 204 (No Content), and 304 (Not Modified) responses do not include content. All other responses do include content, although that content might be of zero length. Corrected Text -------------- All 1xx (Informational), 204 (No Content), 205 (Reset Content), and 304 (Not Modified) responses do not include content. All other responses do include content, although that content might be of zero length. Notes ----- Per section 15.3.6 (205 No Content), it says that servers MUST NOT generate a response. Section 6.4.1 says that "All 1xx, 204, and 304 response don't include content and others do." even though 205 response mustn't generate content. 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
Received on Friday, 11 August 2023 17:52:23 UTC