About 30 sites are open in the browser at any point in time and while that may seem overkill to some, others work with hundreds of sites and have these sites restored on browser start.

One of the things that has been bugging me for a while was that Firefox loaded the sites in question from cache and not the network. I noticed this especially here on Ghacks where no new comments were listed on first start.

Only a refresh of the page, by hitting F5 or Ctrl-F5, loaded the latest version from the server and displayed that there were new comments available.

Having to hit the F5 key regularly on browser start is not something that I'd call practical. There is however no option in Firefox to modify that behavior. While there are options to modify the caching behavior of the browser, only one seems to have an impact on the issue. By moving all cache to memory, Firefox cannot reload data anymore from cache which means that contents are loaded from the network automatically on start.

There is a second, easier option though. Since the loading requires cache to be present, it is also possible to clear the browser cache on exit automatically so that Firefox cannot use it to load site contents.

Here is how that is done:

Tap on the Alt-key on the keyboard and select Tools > Options from the menu that opens up at the top.

Switch to Privacy in the options window.

Select "use custom settings for history" under history.

Check "clear history when Firefox closes" and click on settings next to it.

Firefox clears the cache on exit automatically once setup correctly. This frees up disk space and should not have any ill-effects on the browser or its performance.

All sites restored on start will be loaded from the network from that moment on so that the latest version is always displayed in the browser.

Summary

Article Name

Force Firefox to reload from the network on startup

Description

Firefox will load websites from cache on start of the browser under certain circumstances. This guide tells you how to force the browser to load from the network at all times.

Author

Martin Brinkmann

Advertisement

We need your help

Advertising revenue is falling fast across the Internet, and independently-run sites like Ghacks are hit hardest by it. The advertising model in its current form is coming to an end, and we have to find other ways to continue operating this site.

We are committed to keeping our content free and independent, which means no paywalls, no sponsored posts, no annoying ad formats or subscription fees.

If you like our content, and would like to help, please consider making a contribution:

About Martin Brinkmann

Martin Brinkmann is a journalist from Germany who founded Ghacks Technology News Back in 2005. He is passionate about all things tech and knows the Internet and computers like the back of his hand.You can follow Martin on Facebook, Twitter or Google+

I tried that with Firefox ESR 24.8.1 and it caused the firefox.exe process to hang on close for ~10 minutes. As I was tired of waiting, I killed the process from the Task Manager. When I restarted the browser, it hanged again: the window didn’t appear for 5+ minutes (firefox.exe process showed 50% CPU usage the whole time, as before). After another process killing, I was able to launch Firefox normally. So I reverted your changes. Does it work better on more recent versions of Firefox?

I agree with you. The correct English in this context is practical. However, it is not a case of practicable being old and out of date. Practical as a synonym of useful, and practicable as a synonym of doable and feasible.http://grammarist.com/usage/practical-practicable/

About gHacks

Ghacks is a technology news blog that was founded in 2005 by Martin Brinkmann. It has since then become one of the most popular tech news sites on the Internet with five authors and regular contributions from freelance writers.