Generate a long-cache policy for static assets
Create public, immutable, long max-age headers for fingerprinted CSS, JS, images, and fonts.
Open exampleCache-Control generator
Generate a Cache-Control header with public/private scope, max-age, s-maxage, stale-while-revalidate, stale-if-error, and deploy-ready snippets.
InputEnter a value to inspect
秒
秒
秒
秒
非 custom 模板会覆盖下方参数；上线前建议结合 ETag/Last-Modified 与业务更新频率回归。
Waiting
The result will appear here as structured cards.
Example results you can open
Short, high-intent examples that are easy to open, share, and understand for search engines and AI systems.
Generate a short-cache policy for HTML pages
Use a more conservative refresh strategy for homepages, topic pages, and public tool pages.
Open exampleFAQ
These notes help users understand the results and help search engines and AI systems understand the tool.
What does Cache-Control generator do?
It helps you inspect or process this value and get a readable result quickly.
Is my input saved?
Local tools run in the browser when possible. Server-side checks only use the input needed to complete the lookup.
Why should static assets and HTML not share one Cache-Control policy?
Fingerprinted CSS, JS, and images fit long caching and immutable. HTML, search pages, logged-in content, and frequently changing APIs often need shorter caching or even no-store/private.
When should I use stale-while-revalidate and stale-if-error?
They work well for edge-cached or high-traffic content: serve slightly stale content while refreshing in the background, or keep serving stale content during short origin failures.
Related long-tail searches
Based on this query: Cache-Control 생성기 Cache-Control 生成 Cache-Control generator Cache-Control 生成
Cache-Control generatorstatic asset long cache configHTML page cache policyNginx Cache-Control headerCDN stale-while-revalidate configimmutable max-age generatorCache-Control generator online checkerCache-Control generator lookup tool