Hi Bast,
I noticed that cache control on google chrome isn't working properly.
For the main URL /my-colony/ there isn't any cache control set. Neither at server response level, nor in the index.html. This leads chrome to stick to a cached version like forever. Mine still tries to load version 0.60, which isn't on the server anymore and is stuck at the loading screen.
The files that are included in the index.html all have ETags, Last-Modified dates. This should work for files below the index.html.
Files included from other sources, like the fonts from google are using expires and proper cache control statements.
Please use something like this for the files that change on every update.
cache-control: private, max-age=86400, stale-while-revalidate=86400
For bandwidth saving, more static files may be cached longer of course.
I guess there's also a bug in chrome, that even if you disable the cache or clean it, it loads the old version. If you manage to load the new version, on the next reload it reverts back to the old version. Can't tell why that is. Firefox doesn't have that strange behavior.
Best regards,
BLARG
So, could you tell me how to do this in normal english, all that went over my head and I'm having the same problem
@RangedPies
https://www.ape-apps.com/viewpage.php?p=20933