zlacker

[parent] [thread] 4 comments
1. CmdrKr+(OP)[view] [source] 2023-07-18 14:39:33
Good reason to avoid Firefox for development imo. Nothing is more annoying than mysterious cache interventions when you're trying to get a handle on an unrelated problem.
replies(1): >>bayind+lg
2. bayind+lg[view] [source] 2023-07-18 15:32:51
>>CmdrKr+(OP)
Dev tools automatically disables caching for that tab, by default.

CTRL+SHIFT+R always disables cache for that reload, too.

replies(2): >>aidenn+Hr >>CmdrKr+Eb1
◧◩
3. aidenn+Hr[view] [source] [discussion] 2023-07-18 16:13:41
>>bayind+lg
I didn't know about devtools doing that; C-S R is what I use when I run into it.
replies(1): >>bayind+BF
◧◩◪
4. bayind+BF[view] [source] [discussion] 2023-07-18 17:01:44
>>aidenn+Hr
On the Dev Tools’ network tab, there should be a checkbox about it on the top left.
◧◩
5. CmdrKr+Eb1[view] [source] [discussion] 2023-07-18 19:07:15
>>bayind+lg
In the dev tools settings there is a checkbox "Disable HTTP Cache (when toolbox is open)" which name seems to imply that this only applies to the resources that make up the page, not to DNS lookups (about:config name is devtools.cache.disabled, and it defaults to false).

I investigated and found that Firefox's in-memory DNS cache can be manually cleared by clicking a button in about:networking. To be fair Chrome also has a similar cache and method for clearing it. See: https://www.makeuseof.com/chrome-edge-firefox-safari-opera-b...

[go to top]