rfc9875v2.txt | rfc9875.txt | |||
---|---|---|---|---|
skipping to change at line 12 ¶ | skipping to change at line 12 ¶ | |||
Internet Engineering Task Force (IETF) M. Nottingham | Internet Engineering Task Force (IETF) M. Nottingham | |||
Request for Comments: 9875 Cloudflare | Request for Comments: 9875 Cloudflare | |||
Category: Standards Track October 2025 | Category: Standards Track October 2025 | |||
ISSN: 2070-1721 | ISSN: 2070-1721 | |||
HTTP Cache Groups | HTTP Cache Groups | |||
Abstract | Abstract | |||
This specification introduces a means of describing the relationships | This specification introduces a means of describing the relationships | |||
between stored responses in HTTP caches, "grouping" them by | between stored responses in HTTP caches, grouping them by associating | |||
associating a stored response with one or more strings. | a stored response with one or more strings. | |||
Status of This Memo | Status of This Memo | |||
This is an Internet Standards Track document. | This is an Internet Standards Track document. | |||
This document is a product of the Internet Engineering Task Force | This document is a product of the Internet Engineering Task Force | |||
(IETF). It represents the consensus of the IETF community. It has | (IETF). It represents the consensus of the IETF community. It has | |||
received public review and has been approved for publication by the | received public review and has been approved for publication by the | |||
Internet Engineering Steering Group (IESG). Further information on | Internet Engineering Steering Group (IESG). Further information on | |||
Internet Standards is available in Section 2 of RFC 7841. | Internet Standards is available in Section 2 of RFC 7841. | |||
skipping to change at line 152 ¶ | skipping to change at line 152 ¶ | |||
2. They both share the same URI origin (per Section 4.3.1 of | 2. They both share the same URI origin (per Section 4.3.1 of | |||
[HTTP]). | [HTTP]). | |||
2.2. Cache Behaviour | 2.2. Cache Behaviour | |||
2.2.1. Invalidation | 2.2.1. Invalidation | |||
A cache that invalidates a stored response MAY invalidate any stored | A cache that invalidates a stored response MAY invalidate any stored | |||
responses that share groups (per Section 2.1) with that response. | responses that share groups (per Section 2.1) with that response. | |||
Note that further grouped invalidations are not triggered by a | Note that further grouped invalidations are not triggered by a | |||
grouped invalidation; i.e., this mechanism does not "cascade". | grouped invalidation; i.e., this mechanism does not cascade. | |||
Cache extensions can explicitly strengthen the requirement above. | Cache extensions can explicitly strengthen the requirement above. | |||
For example, a targeted cache control header field [TARGETED] might | For example, a targeted cache control header field [TARGETED] might | |||
specify that caches processing it are required to invalidate such | specify that caches processing it are required to invalidate such | |||
responses. | responses. | |||
3. The Cache-Group-Invalidation Response Header Field | 3. The Cache-Group-Invalidation Response Header Field | |||
The Cache-Group-Invalidation response header field is a List of | The Cache-Group-Invalidation response header field is a List of | |||
Strings (Sections 3.1 and 3.3.3 of [STRUCTURED-FIELDS]). Each member | Strings (Sections 3.1 and 3.3.3 of [STRUCTURED-FIELDS]). Each member | |||
End of changes. 2 change blocks. | ||||
3 lines changed or deleted | 3 lines changed or added | |||
This html diff was produced by rfcdiff 1.48. |