vulns.co
/
GKData.io MCP and API Buy me a coffee

Google Chrome for Developers

Chrome bfcache: restored pages and session-state boundaries

A page restored from Chrome's back/forward cache resumes its saved in-memory state rather than loading again from the network. Chrome's guide explains when pages marked no-store may enter that cache, describes eviction safeguards for authentication changes, and recommends considering a data refresh when a page is restored.

Open the referenceImplementation GuideReviewed 2026-10-03

How to use this reference

Distinguish HTTP cache policy from suspended-page lifetime in an owned application’s session model. Define how sensitive state is cleared or refreshed after restoration and how logout remains effective across navigation. Preserve server-side authorization independently of restored client state.

Before reading

  • Browser origin and navigation concepts
  • HTTP session and response-cache fundamentals

Context and limits

  • Chrome-specific eligibility safeguards must not be generalized to every browser or authentication design.
  • The broader web.dev guide still describes the Chrome change as ongoing; the separately dated Chrome article provides more specific implementation context.
  • No browser execution or live application assessment was performed; this is lifecycle guidance, not an individual vulnerability report.

Sources

  1. Enabling bfcache for Cache-Control: no-storeGoogle Chrome for Developers · reviewed 2026-10-03
  2. Back/forward cacheGoogle web.dev · reviewed 2026-10-03

Record reviewed 2026-10-03. Snapshot a066321c166a. Open the complete JSON contract.

Library synced 2026-11-19 · cases last reviewed 2026-10-05

a066321c166a · JSON exports & schemas · CC BY 4.0 content / MIT software