rfc9211v9.txt		rfc9211.txt
	Internet Engineering Task Force (IETF) M. Nottingham		Internet Engineering Task Force (IETF) M. Nottingham
	Request for Comments: 9211 Fastly		Request for Comments: 9211 Fastly
	Category: Standards Track March 2022		Category: Standards Track June 2022
	ISSN: 2070-1721		ISSN: 2070-1721
	The Cache-Status HTTP Response Header Field		The Cache-Status HTTP Response Header Field
	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		response, explaining how they handled the request in an ad hoc
	manner. This specification defines a standard mechanism to do so		manner. This specification defines a standard mechanism to do so
	that is aligned with HTTP's caching model.		that is aligned with HTTP's caching model.
	skipping to change at line 355 ¶		skipping to change at line 355 ¶
	Reference: [to a specification defining this parameter, if		Reference: [to a specification defining this parameter, if
	available]		available]
	See the registry at <https://www.iana.org/assignments/http-cache-		See the registry at <https://www.iana.org/assignments/http-cache-
	status> for details on where to send registration requests.		status> for details on where to send registration requests.
	5. IANA Considerations		5. IANA Considerations
	IANA has created the "HTTP Cache-Status" registry at		IANA has created the "HTTP Cache-Status" registry at
	<https://iana.org/assignments/http-cache-status> and populated it		<https://www.iana.org/assignments/http-cache-status> and populated it
	with the types defined in Section 2; see Section 4 for its associated		with the types defined in Section 2; see Section 4 for its associated
	procedures.		procedures.
	IANA has added the following entry in the "Hypertext Transfer		IANA has added 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:
	Field name: Cache-Status		Field name: Cache-Status
	Status: permanent		Status: permanent
	Reference: RFC 9211		Reference: RFC 9211
	skipping to change at line 397 ¶		skipping to change at line 397 ¶
	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
	sent with sensitive information (e.g., the key parameter) only when		sent with sensitive information (e.g., the key parameter) only when
	the client is authorized.		the client is authorized.
	7. References		7. References
	7.1. Normative References		7.1. Normative References
	[HTTP] Fielding, R., Ed., Nottingham, M., Ed., and J. Reschke,		[HTTP] Fielding, R., Ed., Nottingham, M., Ed., and J. Reschke,
	Ed., "HTTP Semantics", RFC 9110, DOI 10.17487/RFC9110,		Ed., "HTTP Semantics", STD 97, RFC 9110,
	February 2022, <https://www.rfc-editor.org/info/rfc9110>.		DOI 10.17487/RFC9110, June 2022,
			<https://www.rfc-editor.org/info/rfc9110>.
	[HTTP-CACHING]		[HTTP-CACHING]
	Fielding, R., Ed., Nottingham, M., Ed., and J. Reschke,		Fielding, R., Ed., Nottingham, M., Ed., and J. Reschke,
	Ed., "HTTP Caching", RFC 9111, DOI 10.17487/RFC9111,		Ed., "HTTP Caching", STD 98, RFC 9111,
	February 2022, <https://www.rfc-editor.org/info/rfc9111>.		DOI 10.17487/RFC9111, June 2022,
			<https://www.rfc-editor.org/info/rfc9111>.
	[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>.
	[RFC8126] Cotton, M., Leiba, B., and T. Narten, "Guidelines for		[RFC8126] Cotton, M., Leiba, B., and T. Narten, "Guidelines for
	Writing an IANA Considerations Section in RFCs", BCP 26,		Writing an IANA Considerations Section in RFCs", BCP 26,
	RFC 8126, DOI 10.17487/RFC8126, June 2017,		RFC 8126, DOI 10.17487/RFC8126, June 2017,
	<https://www.rfc-editor.org/info/rfc8126>.		<https://www.rfc-editor.org/info/rfc8126>.
End of changes. 4 change blocks.
	6 lines changed or deleted		8 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/