Open smalers opened 3 years ago
Clearing the browser cache in Chrome inspect caused the resources to display correctly.
S3 seems to have a default expiration of maybe up to 24 hours?
Probably need to implement CloudFront and use invalidation, or maybe configuration that treats some files as not cached.
We have implemented CloudFront for all websites and CloudFront provides invalidation features that should address latency. Keep this issue open for now but close ASAP if CloudFront is performing as expected.
Data layers are uploaded to S3 as data assets for the website. Sometimes the entire application is uploaded, but as appropriate only the
assets
folder is synchronized. Reloading the public website often does not show the new data such as GeoJSON files. The data do become visible later but sometimes the lag can be significant (hours).Checking S3 shows the latest file on S3 so there is also the issue of application not pulling in the latest GeoJSON. This can happen even when using an incognito window. Is it cached? It should not be.
Need to figure out why the delay is significant in some cases.
The issue could be addressed by implementing CloudFront and using invalidation, but that will require additional configuration.
Could also write a script to automate access and check for latest version, to see how long of a delay is typical.