Skip to content
ImpactrStart an engagement

HTTP security header

Cache-Control

Cache-Control governs how responses are cached by browsers and intermediaries. For pages containing sensitive or personalized data, directives like no-store prevent that data from being written to shared or on-disk caches where it could later be exposed.

Example

Cache-Control: no-store

Configuration guidance

  • Use no-store for authenticated or sensitive responses.
  • Avoid caching pages that reflect per-user data on shared proxies.

Related headers

MDN: Cache-Control

Impactr finds and proves whether flaws like this are actually reachable in your own web apps and APIs, with a reproducible exploit as evidence.

Start an engagement
← All security headers