I'm trying to work in my local server but I have to clear my cache every time if I want to see changes on the css rules.
There is any way to control Google Chrome cache?
Add a comment
|
10 Answers
- Open
DevTools - Open
Settings(bottom right or useF1shortcut) - Check
Disable cache (while DevTools is open)
https://developers.google.com/chrome-developer-tools/docs/settings#general
7 Comments
ThomasPeeters
This is the only thing that worked for me to see changes in @imported css files.
MTAdmin
Thank you! This has been driving me crazy for months!
Irfan Ahmed
If I push the css changes over live server, then it does not appears until we refresh the cache, how to resolve this issue? I mean the public users don't know about the changes.
Brien Foss
The strangest thing was happening while I was experiencing this annoyance...Some of the margin, padding, spacing changes I was making to the css file was actually verifiable when I refreshed the page, however just not all of the changes. Changing the setting as noted here was exactly what I needed. Thank you very much!
Walty Yeung
just FYI, it's a checkbox at the top right corner (under network section).
|
- Open up your Developer Tools then click the icon on the top right
- In settings --> preferences scroll down to find "Disable cache (while DevTools is open)" and click on the box to select the option.
If you are still having the problem, and the page works on other browsers, then the easy fix could be to just uninstall Google Chrome and do a fresh install of the latest version. I ran into this problem and it was the best fix instead of the headache of tracking down a complicated fix or outdated posts that no longer work. After you have Chrome reinstalled, repeat the steps above to disable cache.
1 Comment
Anupam
In 2017, this helped me in actually locating the setting
Following this solution here helped me reloading the css : https://wpreset.com/force-reload-cached-css/
Instead of requesting the file doing the following :
<link rel="stylesheet" href="~/css/variabledocument.css" type="text/css" />
Request id by adding a parameter (the name of the parameter doesn't matter) at the end of the file :
<link rel="stylesheet" href="~/css/variabledocument.css?refreshcss=1" type="text/css" />
This will request the new css file. Whenever you make a change to your css file, you just have to change either the parameter name, value or both and the server will request it again.
This is very useful when you have no control over the browsers of your clients and it requests no action on their part.
2 Comments
Anthony Griggs
Simple and effective. Best of all it has kind of a similar "Versioning" method for future updates. Couldn't believe the trouble I had updating a simple CSS file!
DarrenMB
Having issues with subsequent deployments. This method is a nice solution I can centralize in my base web page class for all files. such as appending the build date of the DLL so they only change when the application is recompiled and deployed.
<link rel="stylesheet" href="~/css/variabledocument.css?BD=20201209094326" type="text/css" /> Should work for script files with the same issue too.You can do any of the following options:-
- Install a Chrome Extension like Clear Cache to clear cache by clicking on icon.
- Use Incognito Mode and browser your website in incognito mode. Incognito mode won't disable cache clearly. Disabling cache completely may slow down your browsing experience.
- Use chrome's features like Hard Reload (Clear cache and hard reload). Read this stackoverflow post
- As @Vitaly mentioned, Use Developer Tool settings to disable cache completely.
Choose what fits you :)
Comments
More tools > Developer Tools
Then right click the refresh button on the browser.
You will get three options. Select "Empty Cache and Hard Reload".
This will only impact the active tab.
Comments
Just to elaborate on JGallardo's answer above in 2022
In Chrome version 100.0.4896.88 in order to Disable the cache (while DevTools is open) the setting looks like this:
Comments
Shift-F5 to reload the page worked for me on Chrome 61.0.3163.100
Comments
To Control Google Chrome Cache you can do following steps:
- Disable the cache (while DevTools is open)
- Close the Chrome Browser
- Clear the Cache with a cleaner software (such as CC Cleaner)
- Open Chrome browser
1 Comment
Just Me
doesn't help me at all... :(
I like the solution of SylvainB2347 with adding some parameter to the include statement. This really makes Chrome to reload the resource as it assumes it must have changed.
I just wanted to optimize this solution a little, to make it automatic but not breaking the caching principle.
My solution is to use the PHP function filemtime(filename) which returns the timestamp of last content modification. I use it as:
<link rel="stylesheet" href="/index.css?foo=<?php echo filemtime("index.css"); ?>">
which produces this in HTML:
<link rel="stylesheet" href="/index.css?foo=1673508035">
When I modify index.css, the timestamp changes. This way the browser is forced to reload the resource only if it's been modified since the last visit. And I don't have to rewrite anything manually.
