- From: RFC Errata System <rfc-editor@rfc-editor.org>
- Date: Sun, 20 Sep 2015 14:27:04 -0700 (PDT)
- To: http@florianbest.de, fielding@gbiv.com, mnot@mnot.net, julian.reschke@greenbytes.de
- Cc: barryleiba@computer.org, iesg@ietf.org, ietf-http-wg@w3.org, rfc-editor@rfc-editor.org
The following errata report has been rejected for RFC7234, "Hypertext Transfer Protocol (HTTP/1.1): Caching". -------------------------------------- You may review the report below and at: http://www.rfc-editor.org/errata_search.php?rfc=7234&eid=4479 -------------------------------------- Status: Rejected Type: Editorial Reported by: Florian Best <http@florianbest.de> Date Reported: 2015-09-20 Rejected by: Barry Leiba (IESG) Section: 5.3 Original Text ------------- The Expires value is an HTTP-date timestamp, as defined in <a href="#section-7.1.1.1">Section</a> <a href="#section-7.1.1.1">7.1.1.1</a> of [<a href="./rfc7231" title=""Hypertext Transfer Protocol (HTTP/1.1) : Semantics and Content"">RFC7231</a>]. Corrected Text -------------- The Expires value is an HTTP-date timestamp, as defined in <a href="./rfc7231#section-7.1.1.1">Section</a> <a href="./rfc7231#section-7.1.1.1">7.1.1.1</a> of [<a href="./rfc7231" title=""Hypertext Transfer Protocol (HTTP/1.1) : Semantics and Content"">RFC7231</a>]. Notes ----- The anchor should link to RFC 7231. It links to the not-existing section in RFC 7234 itself. --VERIFIER NOTES-- The links are not in the RFCs, but in the HTML tools rendering. The errata system isn't for that. -------------------------------------- RFC7234 (draft-ietf-httpbis-p6-cache-26) -------------------------------------- Title : Hypertext Transfer Protocol (HTTP/1.1): Caching Publication Date : June 2014 Author(s) : R. Fielding, Ed., M. Nottingham, Ed., J. Reschke, Ed. Category : PROPOSED STANDARD Source : Hypertext Transfer Protocol Bis APP Area : Applications Stream : IETF Verifying Party : IESG
Received on Sunday, 20 September 2015 21:28:17 UTC