We use Cache-Control: no-cache right now, meaning before using cached content, a client has to check in with the server to validate it. The files are mostly static so this is redundant, except when we deploy an acute change to e.g. a JavaScript file.
A better fit would be invalidating the cache only if something actually changed.
There is some prior discussion on this:
#77 (comment)
#77 (comment)
We use
Cache-Control: no-cacheright now, meaning before using cached content, a client has to check in with the server to validate it. The files are mostly static so this is redundant, except when we deploy an acute change to e.g. a JavaScript file.A better fit would be invalidating the cache only if something actually changed.
There is some prior discussion on this:
#77 (comment)
#77 (comment)