I recently noticed a scenario where a web tool loads updated data (via JavaScript and backend API), but the browser (and proxy cache) still serves outdated content when viewed on a different device. Clearing the browser cache fixes it, but that’s not a scalable solution for users. I’m curious: does Firefox’s caching behavior differ for pages that use heavy client-side updates (e.g., incremental [https://aftcalculator.io score calculators]) compared to standard static pages? Should we be explicitly sending cache-control headers like no-store or must-revalidate to prevent stale data? Any documented guidance on how Firefox handles cache revalidation for dynamic web-apps would be helpful. Thanks in advance for any pointers.