Read HTTP Headers to Debug Caching
Users see an old file after a deployment while developers see a new one. This guide gives you a small, testable way to approach the issue before changing a live system.
A practical workflow
- Inspect Cache-Control, ETag and response status from the affected URL.
- Test with and without a cache and document which layer served the response.
What to check
Do not disable all caching permanently to fix a versioned asset problem. Compare the result with the original problem and record what changed. If a measurement or test does not support the change, revisit the assumption rather than adding more complexity.
Keep the experiment small enough to reverse. Document the starting state, the change and the result so another person can repeat the process. Product menus and versions can change, so check the current documentation for your environment.
Official reference: Read the documentation.