読み込み中...
読み込み中...
RFC 9111・5861・8246に基づき、代表的なresponse Cache-Control directive exact8と保存・再利用・freshnessの非保証境界を確認できます。
最終更新日 ・ by yuzlrin
| 項目 | 内容 |
|---|---|
| Cache-Control: no-store | A conformant cache must not store the response; this is not a privacy or security guarantee. (RFC 9111 §5.2.2.5) |
| Cache-Control: no-cache | A cache may store the response but must not reuse it without successful validation by the origin server. (RFC 9111 §5.2.2.4) |
| Cache-Control: max-age=3600 | The response becomes stale when its age exceeds 3600 seconds; storage and 3600 seconds of delivery are not guaranteed. (RFC 9111 §5.2.2.1) |
| Cache-Control: private | The bare directive prohibits a shared cache from storing the response; a private cache may store it under applicable conditions, without a confidentiality guarantee. (RFC 9111 §5.2.2.7) |
| Cache-Control: public | A cache may store the response under the RFC conditions; storage or reuse is not required. (RFC 9111 §5.2.2.9) |
| Cache-Control: must-revalidate | Once stale, the response must not be reused without successful validation; this does not require storage, set freshness, or guarantee availability. (RFC 9111 §5.2.2.2) |
| Cache-Control: stale-while-revalidate=60 | For up to 60 seconds after becoming stale, a cache may serve the stale response while revalidating; serving and asynchronous revalidation are not guaranteed. (RFC 5861 §3) |
| Cache-Control: immutable | While the response is fresh, a client need not send an unnecessary conditional request; this does not mean permanently fresh, permanently unchanged, or that force reload is ignored. (RFC 8246 §2) |