Cache-Control for personalized commerce pages
Edge caching can reduce latency, but a fast cache is harmful if it serves one shopper’s state to another. Start by classifying responses as public, private, or unsafe to store.
What the standard means in practice
Shared caches need explicit rules. Mark personalized responses private or no-store, and cache public assets with validators and deliberate lifetimes.
Set a narrow rule, verify it with production evidence, and keep a rollback path. Review the rule whenever vendors, page behavior, or data flows change.
A practical check
- Write down the intended behavior and exceptions.
- Test both the expected path and a failure path.
- Measure the result in real traffic without collecting more data than needed.
Source
Primary reference: RFC 9111. Reviewed Sep 21, 2026.