Cache-Control explainer
Inspect cache directives and supplied age to understand explicit freshness windows and conflicts.
The example value has been entered. Check it immediately or change the value.
Input is processed in the browser. Refreshing returns a sample value.
Instructions and example
Repeated freshness directives are marked ambiguous rather than declared fresh. With must-revalidate, validation after expiry takes precedence in the explanation.
With max-age=600 and stale-while-revalidate=30, age 620 lies in the stale revalidation window. This alone does not guarantee reuse permission.
The explanation centers on max-age, not live cache state. Full shared-cache, conditional-validation and extension behavior is not computed.
Frequently asked questions
What if max-age repeats or must-revalidate is present?
Repeated freshness directives are marked ambiguous rather than declared fresh. With must-revalidate, validation after expiry takes precedence in the explanation.
Does this prove a browser or CDN actually cached the response?
The explanation centers on max-age, not live cache state. Full shared-cache, conditional-validation and extension behavior is not computed.
Calculation criteria and reference materials
- RFC 9111 — HTTP Caching
The explanation centers on max-age, not live cache state. Full shared-cache, conditional-validation and extension behavior is not computed.
Verification of calculation criteria: · Calculation·verification principles · Report errors