…Section 5.2.2.7 public Section 5.2.2.5 s-maxage Section 5.2.2.9 stale-if-error [RFC5861] Section 4 stale-while-revalidate [RFC5861] Section 3 7.2. Warn Code Registry The "Hypertext Transfer Protocol (HTTP) Warn Codes" registry defines the namespace for warn codes. It has been cre…

…2.7 | public | Section 5.2.2.5 | s-maxage | Section 5.2.2.9 | stale-if-error | [RFC5861], Section 4 | stale-while-revalidate | [RFC5861], Section 3 +------------------------+----------------------------------+ Fielding, et al. Standards Track [Page 33] RFC 7234 HTTP/1.1 Caching J…

…2.7 | public | Section 5.2.2.5 | s-maxage | Section 5.2.2.9 | stale-if-error | [RFC5861], Section 4 | stale-while-revalidate | [RFC5861], Section 3 +------------------------+----------------------------------+ Fielding, et al. Standards Track [Page 33] RFC 7234 HTTP/1.1 Caching J…

…est directive in Section 5.2.1 , extension directives such as those defined in [RFC5861] , or configuration in accordance with an out-of-band contract). 4.3. Validation When a cache has one or more stored responses for a requested URI, but cannot serve any of them (e.g., because …

…2.7 | public | Section 5.2.2.5 | s-maxage | Section 5.2.2.9 | stale-if-error | [RFC5861], Section 4 | stale-while-revalidate | [RFC5861], Section 3 +------------------------+----------------------------------+ Fielding, et al. Standards Track [Page 33] RFC 7234 HTTP/1.1 Caching J…

…| public | Section 5.2.2.5 | | s-maxage | Section 5.2.2.9 | | stale-if-error | [RFC5861], Section 4 | | stale-while-revalidate | [RFC5861], Section 3 | +------------------------+----------------------------------+ Fielding, et al. Standards Track [Page 33] RFC 7234 HTTP/1.1 Cachi…

…2.7 | public | Section 5.2.2.5 | s-maxage | Section 5.2.2.9 | stale-if-error | [RFC5861], Section 4 | stale-while-revalidate | [RFC5861], Section 3 +------------------------+----------------------------------+ Fielding, et al. Standards Track [Page 33] RFC 7234 HTTP/1.1 Caching J…

…08 ]). The stale-while-revalidate and stale-if-error Cache-Control directives [ RFC5861 ] could be well suited to a DoH implementation when allowed by server policy. Those mechanisms allow a client, at the server's discretion, to reuse an HTTP cache entry that is no longer fresh.…

…y". Issuers SHOULD use HTTP cache directives to permit caching of this resource RFC5861 , as defined in the issuance ISSUANCE protocol. 4. Token Challenge Requirements Clients receive challenges for tokens, as described in AUTHSCHEME For the rate-limited token issuance protocol d…

…blic RFC9111, Section 5.2.2.9 s-maxage RFC9111, Section 5.2.2.10 stale-if-error RFC5861, Section 4 stale-while-revalidate RFC5861, Section 3

…regators SHOULD use HTTP caching to permit client-side caching of this resource RFC5861 . Aggregators SHOULD favor long cache lifetimes to avoid frequent cache revalidation, e.g., on the order of days. Aggregators can control this cached lifetime with the Cache-Control header, as…

…uest directive in Section 5.2.1 , extension directives such as those defined in RFC5861 , or configuration in accordance with an out-of-band contract). 4.3. Validation When a cache has one or more stored responses for a requested URI, but cannot serve any of them (e.g., because t…

…uest directive in Section 5.2.1, extension directives such as those defined in [RFC5861], or configuration in accordance with an out-of-band contract). 4.3. Validation When a cache has one or more stored responses for a requested URI, but cannot serve any of them (e.g., because t…

…blic RFC9111, Section 5.2.2.9 s-maxage RFC9111, Section 5.2.2.10 stale-if-error RFC5861, Section 4 stale-while-revalidate RFC5861, Section 3

…uest directive in Section 5.2.1 , extension directives such as those defined in RFC5861 , or configuration in accordance with an out-of-band contract). 4.3. Validation When a cache has one or more stored responses for a requested URI, but cannot serve any of them (e.g., because t…