Very Sorry to Have to Ask - Disable Cache for Development
I made a mistake and broke my FireFox profile. I made a new profile, then copied 11 files from a backup of my profile into my new profile folder, following these instructions https://support.mozilla.org/en-US/kb/recovering-important-data-from-an-old-profile
Most things came right back, that is very nice.
I am not certain if browser cache is disabled, which is necessary to avoid insanity while making changes to websites, which is what I do all the time. My mental defects did not prevent me finding thousands of web pages explaining how to complete this task. However, my mental defects prevented me finding any explanation created since the formation of the internet (I am estimating the internet first formed in 2008, because the dates of the answers I found indicated as such (anything before 2013 is basically the same as 2008 for internet purposes). And so, I am here to beg a moment of your time to help me resolve this risk to my mental health which will be extremely serious if caching does not discontinue its anti-social activities.
LEST YOU THINK I AM HELPLESS I found my way to about:config, entered cache into the search and up came about eighty various cache, assundry and other forms of affiliated/associated items. The list is diverse, but every item on the list has one very special thing in common with all the others, and as a group, they achieve an astonishing feat.
WHAT THESE configs HAVE IN COMMON All eighty configs produce by the procedures above have the letters c-a-c-h-e somewhere within them in that precise sequence, with no intervening or otherwise contrary letterizations.
THEIR COLLECTIVE FEAT They manage to organize themselves to perfection, including among them every single config containing the letters c-a-c-h-e in that exact order. No slackers calling in with covid or excuses of dogs eating their homework, all do their part in the roll call when its taken this way. This kind of character is exemplary and inspiring.
THE PROBLEM I attempted to calculate how many combinations of values these eighty configs can have. I got as far as determining a penny for each combination would amount to more than 400 times the gross product of economic activity since the dawn of recorded history.
STRATEGY Since trying every combination is too time consuming, my goal is to go straight to the correct config adjustment to send the cache away.
HYPOTHESIS Changing the last item on the list, marked 'cache' from TRUE to FALSE will produce the cacheless experience I must achieve in order to not impersonate a Molotov Cocktail.
The attached image shows what I have in mind. I am going ahead with experiements, but my hope is someone with knowledge will help click this thing in the way it should go.
השתנתה ב־ על־ידי Carla Rogers
פתרון נבחר
You can reload web page(s) and bypass the cache to refresh possibly outdated or corrupted files.
- hold down the Shift key and left-click the Reload button
- press "Ctrl + F5" or press "Ctrl + Shift + R" (Windows,Linux)
- press "Command + Shift + R" (Mac)
Prefs for the cache are found under browser.cache*enable
Keep in mind that Firefox needs caches in order to work properly.
For development there is a setting in the developer tools settings to disable the HTTP cache while the developer tools are open (visible).
- devtools.cache.disabled = true
- https://developer.mozilla.org/en-US/Tools/Settings
כל התגובות (6)
I tried updating the picture in the question, but was stymied.
helllo..,
no sorry to ask it's your right and thank you to ask this question.
Sometimes (when your are developing) you may want to force fetching all content fresh all the time including images, resources such as style sheet etc. To facilitate this you can do the following:
Open a new window or tab in Firefox. Type about:config in the address bar. Search for “cache” in the search bar and look for network.http.use-cache in the filtered results. Double-click it will toggle it from “true” to “false”. Default should be “true”. And you’re all set.
Sometime you want to force the cache on one particular page\request. You can do that by holding the “Shift” key while clicking reload or F5.
השתנתה ב־ על־ידי Himanshu prabhakar
פתרון נבחר
You can reload web page(s) and bypass the cache to refresh possibly outdated or corrupted files.
- hold down the Shift key and left-click the Reload button
- press "Ctrl + F5" or press "Ctrl + Shift + R" (Windows,Linux)
- press "Command + Shift + R" (Mac)
Prefs for the cache are found under browser.cache*enable
Keep in mind that Firefox needs caches in order to work properly.
For development there is a setting in the developer tools settings to disable the HTTP cache while the developer tools are open (visible).
- devtools.cache.disabled = true
- https://developer.mozilla.org/en-US/Tools/Settings
Himanshu prabhakar said
helllo.., no sorry to ask it's your right and thank you to ask this question. Sometimes (when your are developing) you may want to force fetching all content fresh all the time including images, resources such as style sheet etc. To facilitate this you can do the following: Open a new window or tab in Firefox. Type about:config in the address bar. Search for “cache” in the search bar and look for network.http.use-cache in the filtered results. Double-click it will toggle it from “true” to “false”. Default should be “true”. And you’re all set. Sometime you want to force the cache on one particular page\request. You can do that by holding the “Shift” key while clicking reload or F5.
This situation is murky. I am not certain, but it looks like network.http.use-cache might not be a part of firefox anymore. It will come up in search, and so will anything entered into config search. The first two attached images show what I am looking at..
The third attached image shows mixed messages on the matter.
השתנתה ב־ על־ידי Carla Rogers
cor-el said
<snip> Prefs for the cache are found under browser.cache*enable
Keep in mind that Firefox needs caches in order to work properly. For development there is a setting in the developer tools settings to disable the HTTP cache while the developer tools are open (visible).
- devtools.cache.disabled = true
- https://developer.mozilla.org/en-US/Tools/Settings
As usual, the information you provide is most informative.
A couple years ago, in a zeal of anti-caching fervor, I disabled all cache config choices I could find. From that point forward, the browser didn't work too good.
The fact there is no one config option for this well-known purpose possibly is due to there is no one way to do it that works for everything while still keeping the browser running well. I think different people do it in different ways.
But then, I just found this: I am going to try this set to 2 (default is 3):
Browser.cache.check doc frequency When a page is loaded, it is cached so it doesn't need to be downloaded to be redisplayed. If the page changes after a previous visit, you may want to redownload it anyway to get the updated page. This preference controls how often to check for a newer version of a cached page. Possible values and their effects 0 Check for a new version of a page once per session (a session starts when the first application window opens and ends when the last application window closes). 1 Check for a new version every time a page is loaded. 2 Never check for a new version - always load the page from cache. 3 Check for a new version when the page is out of date. (Default) Caveats browser.cache.disk.enable or browser.cache.memory.enable must be set to true for this preference to work as mentioned above. http://kb.mozillazine.org/Browser.cache.check_doc_frequency
השתנתה ב־ על־ידי Carla Rogers
If you use as Private Browsing Window you will not need to clear the cache. If you do need to overide the cache for an individual site reload with Keyboard Shortcut Ctrl+F5