Closed TomGijselinck closed 8 years ago
When the webapp get's updated on the server, users still use the old version which is cached by the browser.
The js files get a fingerprint, so these files should get updated. I can only assume that the index page is not refreshed.
Maybe a caching problem. Check this excellent post from Jake Archibald about caching best practices.
Updating the webpage by refreshing solved the problem. Conclusion: it's a caching problem
When the webapp get's updated on the server, users still use the old version which is cached by the browser.
The js files get a fingerprint, so these files should get updated. I can only assume that the index page is not refreshed.
Maybe a caching problem. Check this excellent post from Jake Archibald about caching best practices.
Update
Updating the webpage by refreshing solved the problem. Conclusion: it's a caching problem