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.
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 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-storeon normal pagesunloadevent listener- Open WebSocket/IndexedDB transactions
window.openerreferences- Unsupported APIs in use
⚡ Quick fix
- Use
no-cacheormax-age=0, must-revalidateinstead ofno-store - Replace
unloadwithpagehide - Test in DevTools → bfcache
Detailed fix by platform
JavaScript
window.addEventListener("pageshow", e => { if (e.persisted) refreshData(); });
How to diagnose
- no-store — Used?
- unload — Present?
- 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:
Similar errors
Most viewed in HTTP
Other ways to find it
Where this error sits
Origin: Network. Errors that are often confused with or caused by this one (click to open):
🧠 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.
Report a correction or suggest an improvement
Last updated 18 Nov 2026