What are the important limits?

No server changes occur. no-store overrides the other settings; no-cache permits storage but requires validation. Public must never be used for private user content. Immutable assumes a content-versioned URL. Test actual behavior before deployment.

Where is my information stored?

Processing happens in your browser. These workspaces do not upload your inputs or send reports to a server. Session data is not automatically saved; download a project or report before closing. Keep sensitive exports private.

HTTP Cache-Control Policy Builder

Build browser and CDN cache policies with explicit freshness, revalidation and privacy settings.

Local Developer Workbench

Cache-Control · Response Policy

Files are processed in this browser. No requests are sent to your endpoints.

Cache ScopeBrowser Freshness (seconds)Shared Cache Freshness (seconds)Stale While Revalidating (seconds)

Never store this responseRevalidate before reuseDo not serve stale without validationContent never changes at this URL

no-store overrides all other settings. no-cache allows storage but requires validation. Stale reuse is omitted when no-cache or must-revalidate is selected; immutable is omitted for zero freshness or no-cache.

Cache-Control: private, max-age=0, no-cache

Storage is allowed, but reuse requires successful validation.

Planning aid only. This does not update your server or CDN. Test response headers and cache behavior before production; never mark private user content public.

Loading Tool…

What Is the HTTP Cache-Control Policy Builder?

A response-header planning tool covering public/private scope, max-age, s-maxage, no-store, no-cache, immutable, must-revalidate and stale-while-revalidate. Presets cover personalized HTML, versioned assets, public CDN content and sensitive responses.

How It Works

Choose the response type, enter freshness durations in seconds, and enable relevant options. Read the resulting header and explanatory notes. Copy or download TXT/PDF, then apply deliberately in your server or CDN configuration.

When to Use It

Use when inspecting local developer data or preparing configuration that needs review before production.

Frequently Asked Questions

How do I get started?: Choose the response type, enter freshness durations in seconds, and enable relevant options. Read the resulting header and explanatory notes. Copy or download TXT/PDF, then apply deliberately in your server or CDN configuration.
What are the important limits?: No server changes occur. no-store overrides the other settings; no-cache permits storage but requires validation. Public must never be used for private user content. Immutable assumes a content-versioned URL. Test actual behavior before deployment.
Where is my information stored?: Processing happens in your browser. These workspaces do not upload your inputs or send reports to a server. Session data is not automatically saved; download a project or report before closing. Keep sensitive exports private.

Found an issue? Send Feedback. See our data sources and update policy for tools that depend on changing information.