I have a CF Workers Site site and I notice that the first load after a content change, the browser displays stale content until a hard refresh.
The site is generated by a static site generator (11ty), deployed to CF with GH actions. I notice the behavior in both Safari and Chrome.
I’m thinking the solution for this might be to use a different browser caching strategy. Instead of having the browser cache the page, like etags, but I since CF is hosting their Workers site via Workers, there might be a better strategy.
Also, any examples of manipulating headers in a CF Workers site would be appreciated!