Caching has always been broken. "There are only two hard things in Computer Science: cache invalidation and naming things." -- Phil Karlton, around 1996 or 199

Caching has always been broken. "There are only two hard things in Computer Science: cache invalidation and naming things." -- Phil Karlton, around 1996 or 1997. There are "cache busting" techniques that mostly work, appending a random string as a url parameter https:example.org/path/page.html?5trf6783gf7rvf5 will _almost_ always fetch a current version of the page from origin. If you have stuff where being able to bypass the caches that are out off your control between you and your users, it's worth making sure you have a way to do that. I always use date stamps on things like T&C and Privacy Policy pages, so the actual URL changes when the policies/legals change. So use something like https://example.org/privacy_20220204.html https://example.org/privacy_20220204.html - and make sure you have a good way to update all your internal links and redirect requests to old versions to the new one (or leave the old one in place with a big notice at the top saying "This policy was superseded on 4 Feb 2022 - click here for the current privacy policy")