zlacker

In the past, at least, firefox has done its own caching since expiring my OS dns cache was insufficient to get it to pick up a change in DNS.

>>aidenn+(OP)
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.

>>CmdrKr+Bf
Dev tools automatically disables caching for that tab, by default.

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

>>bayind+Wv
I didn't know about devtools doing that; C-S R is what I use when I run into it.

>>aidenn+iH
On the Dev Tools’ network tab, there should be a checkbox about it on the top left.

>>bayind+Wv
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...