Closed horner closed 2 years ago
@wreiske do you think we should add the url or fix cloudflare?
@horner, IMO, best would be if you can change main.css to ${sha256('main.css')} like meteor. That way even when certain browsers ignore query strings, you'll always have the correct file.
Notice the CF-cache-status was MISS.... That wasn't cloudflare that had cached it at that point. It was safari respecting the cache-control. Maybe nginx or whatever is serving it added that? Cloudflare may have added the cache control, but would refresh the cache automatically after a certain time. It pulls from origin after a defined time to refresh the cache of any changes.
Adding a hash after, like main.css?h=shaOfMainCSS() doesn't always work because certain caches ignore query strings and only respect the file name.
@wreiske thanks, I assigned this back to @ggodlewski
See screenshot below. https://stackoverflow.com/questions/54326697/safari-caching-get-request-even-with-disabled-cache
Greg suggested he add the hash or /api/user?ts=18284 to the URL, but I wanted to make sure this was necessary before we did this.