draft-ietf-httpbis-cache-header-10.txt   draft-ietf-httpbis-cache-header-latest.txt 
HTTP Working Group M. Nottingham HTTP Working Group M. Nottingham
Internet-Draft Fastly Internet-Draft Fastly
Intended status: Standards Track August 17, 2021 Intended status: Standards Track January 14, 2022
Expires: February 18, 2022 Expires: July 18, 2022
The Cache-Status HTTP Response Header Field The Cache-Status HTTP Response Header Field
draft-ietf-httpbis-cache-header-10 draft-ietf-httpbis-cache-header-latest
Abstract Abstract
To aid debugging, HTTP caches often append header fields to a To aid debugging, HTTP caches often append header fields to a
response explaining how they handled the request in an ad hoc manner. response explaining how they handled the request in an ad hoc manner.
This specification defines a standard mechanism to do so that is This specification defines a standard mechanism to do so that is
aligned with HTTP's caching model. aligned with HTTP's caching model.
Note to Readers Discussion Venues
_RFC EDITOR: please remove this section before publication_ This note is to be removed before publishing as an RFC.
Discussion of this draft takes place on the HTTP working group Discussion of this document takes place on the HTTP Working Group
mailing list (ietf-http-wg@w3.org), which is archived at mailing list (ietf-http-wg@w3.org), which is archived at
https://lists.w3.org/Archives/Public/ietf-http-wg/ [1]. <https://lists.w3.org/Archives/Public/ietf-http-wg/>.
Working Group information can be found at https://httpwg.org/ [2];
source code and issues list for this draft can be found at
https://github.com/httpwg/http-extensions/labels/cache-header [3].
Status of This Memo Status of This Memo
This Internet-Draft is submitted in full conformance with the This Internet-Draft is submitted in full conformance with the
provisions of BCP 78 and BCP 79. provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet- working documents as Internet-Drafts. The list of current Internet-
Drafts is at https://datatracker.ietf.org/drafts/current/. Drafts is at https://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
This Internet-Draft will expire on February 18, 2022. This Internet-Draft will expire on July 18, 2022.
Copyright Notice Copyright Notice
Copyright (c) 2021 IETF Trust and the persons identified as the Copyright (c) 2022 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(https://trustee.ietf.org/license-info) in effect on the date of (https://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with respect carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as the Trust Legal Provisions and are provided without warranty as
skipping to change at page 8, line 11 skipping to change at page 8, line 4
value cannot be agreed upon in the community, the parameter's name value cannot be agreed upon in the community, the parameter's name
should be correspondingly specific (e.g., with a prefix that should be correspondingly specific (e.g., with a prefix that
identifies the vendor, application or deployment). identifies the vendor, application or deployment).
Registration requests should use the following template: Registration requests should use the following template:
o Name: [a name for the Cache-Status Parameter that matches the o Name: [a name for the Cache-Status Parameter that matches the
'key' ABNF rule] 'key' ABNF rule]
o Description: [a description of the parameter semantics and value] o Description: [a description of the parameter semantics and value]
o Reference: [to a specification defining this parameter, if o Reference: [to a specification defining this parameter, if
available] available]
See the registry at https://iana.org/assignments/http-cache-status See the registry at https://iana.org/assignments/http-cache-status
[4] for details on where to send registration requests. [1] for details on where to send registration requests.
5. IANA Considerations 5. IANA Considerations
Upon publication, please create the HTTP Cache-Status Parameters Upon publication, please create the HTTP Cache-Status Parameters
registry at https://iana.org/assignments/http-cache-status [5] and registry at https://iana.org/assignments/http-cache-status [2] and
populate it with the types defined in Section 2; see Section 4 for populate it with the types defined in Section 2; see Section 4 for
its associated procedures. its associated procedures.
Also, please create the following entry in the Hypertext Transfer Also, please create the following entry in the Hypertext Transfer
Protocol (HTTP) Field Name Registry defined in [HTTP], Section 18.4: Protocol (HTTP) Field Name Registry defined in [HTTP], Section 18.4:
o Field name: Cache-Status o Field name: Cache-Status
o Status: permanent o Status: permanent
skipping to change at page 9, line 18 skipping to change at page 9, line 12
To avoid assisting such attacks, the Cache-Status header field can be To avoid assisting such attacks, the Cache-Status header field can be
omitted, only sent when the client is authorized to receive it, or omitted, only sent when the client is authorized to receive it, or
only send sensitive information (e.g., the key parameter) when the only send sensitive information (e.g., the key parameter) when the
client is authorized. client is authorized.
7. References 7. References
7.1. Normative References 7.1. Normative References
[HTTP] Fielding, R. T., Nottingham, M., and J. Reschke, "HTTP [HTTP] Fielding, R. T., Nottingham, M., and J. Reschke, "HTTP
Semantics", draft-ietf-httpbis-semantics-17 (work in Semantics", draft-ietf-httpbis-semantics-19 (work in
progress), July 2021. progress), September 2021.
[HTTP-CACHING] [HTTP-CACHING]
Fielding, R. T., Nottingham, M., and J. Reschke, "HTTP Fielding, R. T., Nottingham, M., and J. Reschke, "HTTP
Caching", draft-ietf-httpbis-cache-17 (work in progress), Caching", draft-ietf-httpbis-cache-19 (work in progress),
July 2021. September 2021.
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, Requirement Levels", BCP 14, RFC 2119,
DOI 10.17487/RFC2119, March 1997, DOI 10.17487/RFC2119, March 1997,
<https://www.rfc-editor.org/info/rfc2119>. <https://www.rfc-editor.org/info/rfc2119>.
[RFC5234] Crocker, D., Ed. and P. Overell, "Augmented BNF for Syntax [RFC5234] Crocker, D., Ed. and P. Overell, "Augmented BNF for Syntax
Specifications: ABNF", STD 68, RFC 5234, Specifications: ABNF", STD 68, RFC 5234,
DOI 10.17487/RFC5234, January 2008, DOI 10.17487/RFC5234, January 2008,
<https://www.rfc-editor.org/info/rfc5234>. <https://www.rfc-editor.org/info/rfc5234>.
skipping to change at page 10, line 15 skipping to change at page 10, line 7
7.2. Informative References 7.2. Informative References
[ENTANGLE] [ENTANGLE]
Kettle, J., "Web Cache Entanglement: Novel Pathways to Kettle, J., "Web Cache Entanglement: Novel Pathways to
Poisoning", 2020, <https://i.blackhat.com/USA- Poisoning", 2020, <https://i.blackhat.com/USA-
20/Wednesday/us-20-Kettle-Web-Cache-Entanglement-Novel- 20/Wednesday/us-20-Kettle-Web-Cache-Entanglement-Novel-
Pathways-To-Poisoning-wp.pdf>. Pathways-To-Poisoning-wp.pdf>.
7.3. URIs 7.3. URIs
[1] https://lists.w3.org/Archives/Public/ietf-http-wg/ [1] https://iana.org/assignments/http-cache-status
[2] https://httpwg.org/
[3] https://github.com/httpwg/http-extensions/labels/cache-header
[4] https://iana.org/assignments/http-cache-status
[5] https://iana.org/assignments/http-cache-status [2] https://iana.org/assignments/http-cache-status
Author's Address Author's Address
Mark Nottingham Mark Nottingham
Fastly Fastly
Prahran, VIC Prahran
Australia Australia
Email: mnot@mnot.net Email: mnot@mnot.net
URI: https://www.mnot.net/ URI: https://www.mnot.net/
 End of changes. 16 change blocks. 
29 lines changed or deleted 18 lines changed or added

This html diff was produced by rfcdiff 1.48. The latest version is available from http://tools.ietf.org/tools/rfcdiff/