Hence, select only a few files which often get modified. css files get downloaded, then it will decrease the performance. For every refresh of the page, if all of its associated. Because caching is essential for performance point of view. Analyze which files often get modified and apply a cache busting mechanism only to those files. Therefore, cache buster query string can be updated so that the browser doesn't recognize the file in the cache memory and downloads the new file on a refresh of the page.ĭo not do for all. As a developer, we need to ensure that client's browser should get these updates in existing files without much struggle. css files and update the production environment, the client's browser may not be able to get to see upon refreshing the page as it has cached those files during previous page refresh.

Whenever we do some changes to any of the existing. Now, there can be an issue with this process. When a webpage is downloaded, then its associated files are also downloaded and stored in the browser's cache on the user’s machine.This has to happen as this process improves the performance where the page doesn't need to download these associated files again and again whenever the page is refreshed. It is a unique string appended to the path of the. So, we can hack this through an approach called Cache Busting. We cannot even ask them to go for a hard refresh of the page. The user either has to clear the browser cookie & reload the page or else he or she has to do a hard refresh of the page by pressing Ctrl+F5.īut, we cannot ask each and every user to clear the cookie of their browser. css files. That is the reason those new changes will not appear to the user. When the user accesses the URL, it will take the cached. js files have been cached in the browser. css files and move them to a production environment, those changes may not get reflected in the browser of the customer who is using our software. Whenever we do some modification to the existing.

Chrome force refresh not working