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
{{ message }}
This repository has been archived by the owner on Jan 17, 2023. It is now read-only.
We encountered an issue where an old JavaScript file got cached under a new revision, due to race conditions in the deployment (e.g., someone gets a new app page, but when getting the JavaScript they get routed to an old app server).
I think a simple and fairly safe fix would be to check the ?rev, and if it doesn't match what we expect, then don't let the response be cached. Then everything will mostly work during the deployment (old files will probably work), but old files won't get cached.
The text was updated successfully, but these errors were encountered:
ianb
added
the
ops
Something related to our server hosting and deployments
label
Jan 10, 2018
We encountered an issue where an old JavaScript file got cached under a new revision, due to race conditions in the deployment (e.g., someone gets a new app page, but when getting the JavaScript they get routed to an old app server).
I think a simple and fairly safe fix would be to check the
?rev
, and if it doesn't match what we expect, then don't let the response be cached. Then everything will mostly work during the deployment (old files will probably work), but old files won't get cached.The text was updated successfully, but these errors were encountered: