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 September 13, 2021
Expires: February 18, 2022 Expires: March 17, 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 Note to Readers
skipping to change at page 1, line 45 skipping to change at page 1, line 45
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 March 17, 2022.
Copyright Notice Copyright Notice
Copyright (c) 2021 IETF Trust and the persons identified as the Copyright (c) 2021 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
skipping to change at page 9, line 18 skipping to change at page 9, line 18
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 29 skipping to change at page 10, line 29
[3] https://github.com/httpwg/http-extensions/labels/cache-header [3] https://github.com/httpwg/http-extensions/labels/cache-header
[4] https://iana.org/assignments/http-cache-status [4] https://iana.org/assignments/http-cache-status
[5] https://iana.org/assignments/http-cache-status [5] 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. 6 change blocks. 
9 lines changed or deleted 9 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/