Myth: Cache-Control: no-cache stops caching

Myth: Cache-Control: no-cache stops caching
This week in caching, the most mis-named header in HTTP:
— What people think: no-cache = do not store this.
— What it actually does: no-cache stores the response but forces revalidation before reuse. The directive that prevents storage is no-store.
— Worth your time: for genuinely private data (account pages, tokens) you want no-store, often with private. Using no-cache there leaves a cacheable copy sitting in intermediaries.
Bookmark: no-cache = 'check first', no-store = 'never keep'. Mix them up on a billing page and you've cached someone's invoice. A classic from the HTTP spec footguns.