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
We've been seeing some consistency issues in our static site during the 30 seconds that we are deploying a new version. In our use case, all of the files have a hash appended to the filename, and we use redirects to control which one is "current".
Since some of these files point to eachother, if we upload a new hash for an index file which points to a new hash of another file, and the redirect for the index file points to the new hash, we can get a 404 on trying to access the other file since it hasn't been uploaded yet. This 404 is resolved within 30 seconds when the other file gets uploaded.
We would like the option to enqueue all redirects at the end of the upload queue, after all the uploads have finished. Our proposed solution is a flag that, when true, awaits the klaw stream before pushing the redirect objects to the upload queue. Something like:
Hello,
We've been seeing some consistency issues in our static site during the 30 seconds that we are deploying a new version. In our use case, all of the files have a hash appended to the filename, and we use redirects to control which one is "current".
Since some of these files point to eachother, if we upload a new hash for an index file which points to a new hash of another file, and the redirect for the index file points to the new hash, we can get a 404 on trying to access the other file since it hasn't been uploaded yet. This 404 is resolved within 30 seconds when the other file gets uploaded.
We would like the option to enqueue all redirects at the end of the upload queue, after all the uploads have finished. Our proposed solution is a flag that, when true, awaits the
klaw
stream before pushing the redirect objects to the upload queue. Something like:The text was updated successfully, but these errors were encountered: