You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
With the caching issues described in #316, it may be worth updating the headers we send with static files. Our current headers include a max-age of 12 months, which is useful most of the time, but has started to run into some issues in certain situations. Calculating an ETag for some file requests and shortening this cache duration could be helpful in getting CloudFront to properly update its CDN caches when necessary. Updating our request handling to also react to receiving these ETags could also save us from having to serve the files even if they aren't updated.
The text was updated successfully, but these errors were encountered:
This is a bit more work to implement than ETAGs (because of the hash based uri), but I think it is the correct way, and in the very least I think everyone should read this, so I share it here:
With the caching issues described in #316, it may be worth updating the headers we send with static files. Our current headers include a
max-age
of 12 months, which is useful most of the time, but has started to run into some issues in certain situations. Calculating an ETag for some file requests and shortening this cache duration could be helpful in getting CloudFront to properly update its CDN caches when necessary. Updating our request handling to also react to receiving these ETags could also save us from having to serve the files even if they aren't updated.The text was updated successfully, but these errors were encountered: