Cache-Control HTTP Origin: Network OSI layer 7 · Application Last updated 18 Nov 2026

Back/forward cache blocked by Cache-Control: no-store (stale or reloaded page on Back)

Pressing Back reloads the page from scratch instead of restoring it instantly, or shows stale/old data.

Exact message you may see Back/forward cache not usedPage not eligible for back/forward cacheCache-Control: no-store bfcachebfcache blocked by unload handlerPages with Cache-Control: no-store cannot enter back/forward cache
Seen on: HTTP Chrome Browser

Meaning

Cache-Control: no-store (and unload handlers, open connections) disables the browser's back/forward cache. Use no-cache instead when freshness matters, drop unload listeners (use pagehide), and check DevTools → Application → Back/forward cache.

Common causes

  • Cache-Control: no-store on normal pages
  • unload event listener
  • Open WebSocket/IndexedDB transactions
  • window.opener references
  • Unsupported APIs in use

⚡ Quick fix

  1. Use no-cache or max-age=0, must-revalidate instead of no-store
  2. Replace unload with pagehide
  3. Test in DevTools → bfcache

Detailed fix by platform

JavaScript

  1. window.addEventListener("pageshow", e => { if (e.persisted) refreshData(); });

How to diagnose

  1. no-store — Used?
  2. unload — Present?
  3. bfcache test — Fails?

🔧 Still not fixed?

Many errors look alike. If the steps above didn’t solve it, one of these is probably what you’re facing:

Where this error sits

Origin: Network. Errors that are often confused with or caused by this one (click to open):

404 — 404 on JS/CSS assets after a new deploy (HTTP)404Cache-Control — CDN not caching: Cache-Control private / no-cache / Set-Cookie on the response (HTTP)Cache-ControlCDN cache — CDN or browser serving stale content after a deploy (HTTP)CDN cacheDomain still resolves to the old IP (DNS propagation/cache) — Networking: DNS changed but the domain still resolves to the old IP — TTL and resolver caching ("propagation") (Networking)Domain still resolves…ERR_CACHE_MISS — ERR_CACHE_MISS: Confirm Form Resubmission (Browser)ERR_CACHE_MISSETag — Conditional requests always return 200 (ETag/Last-Modified never matches) (HTTP)ETagVary — Cache hit rate collapses: Vary: Cookie or Vary: * on responses (HTTP)VaryVary: Origin — CORS responses cached for the wrong origin (missing Vary: Origin) (HTTP)Vary: OriginCache-Con…

Explore the map of this error Full error map →

🧠 Still stuck? Analyze your error

Paste the full message, response headers or stack trace — we'll detect the platform and point to the most likely cause.

💬 What worked for others

No tips yet — did something else fix this for you?

Share what worked for you

Tips are checked by an editor before they appear. Links are removed.