- From: RFC Errata System <rfc-editor@rfc-editor.org>
- Date: Sun, 12 Apr 2015 19:41:47 -0700 (PDT)
- To: fielding@gbiv.com, mnot@mnot.net, julian.reschke@greenbytes.de, barryleiba@computer.org, mnot@mnot.net
- Cc: antonio.ignacio.vera@gmail.com, ietf-http-wg@w3.org, rfc-editor@rfc-editor.org
The following errata report has been submitted 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=4334 -------------------------------------- Type: Editorial Reported by: Antonio Vera <antonio.ignacio.vera@gmail.com> Section: 5.3 Original Text ------------- The Expires value is an HTTP-date timestamp, as defined in Section 7.1.1.1 of [RFC7231]. Corrected Text -------------- The Expires value is an HTTP-date timestamp, as defined in Section 7.1.1.1 of [RFC7231]. Notes ----- There's no error in the text itself, but the address of the link in 7.1.1.1 is pointing to a hashtag in RFC 7234, not RFC 7231 as it should. Currently, 7.1.1.1 points to: http://tools.ietf.org/html/rfc7234#section-7.1.1.1 It should point to: http://tools.ietf.org/html/rfc7231#section-7.1.1.1 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 (IESG) can log in to change the status and edit the report, if necessary. -------------------------------------- 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 Area : Applications Stream : IETF Verifying Party : IESG
Received on Monday, 13 April 2015 02:42:53 UTC