Skip to main content

Your Browser and Upstream Caches

Many problems which are reported by bloggers have simple resolution procedures.
Clear cache in the browser, and restart the browser.
Some problems are slightly more complex.
Clear both cache and cookies, and restart the browser.
and, at the center of each procedure, we see
Clear cache.

Cache, or local storage of Internet content, is at the center of many problems with blogs and web sites. If a copy of your blog is in a cache somewhere, the computers that access the cached copy will continue to display that copy, until told to get a fresh copy.

If you just updated your blog, folks accessing the cached copy won't see your changes. One way to ensure that you see fresh copies of everything is to clear cache, which forces fresh retrieval of everything.

For all of its simplicity, clearing cache isn't a universal solution, and neither is it consistently productive - even for problems which are generally known to respond to clearing of cache.

Have you ever noticed that, after you access a new web site, any subsequent visits to that web site seem faster?

Cache reduces load on network resources, by retaining local copies of data.
That's not your imagination, that's your browser using cached content. Caching reduces load time, and it reduces network and server load, by not retrieving directly from a web site, every time you visit that web site.

Clearing cache won't solve all problems - and it may cause more problems.
If you clear cache gratuitously, you increase network and server load for everybody, and slow down everybody's Internet experience.

Besides slowing down the Internet for everybody, clearing cache won't consistently solve your problems. If you clear your cache, that ensure that you get a fresh copy of your blog (and other web sites).

This has nothing to do with what your readers see. And you can only clear the cache that you control.

Some networks cache content, in a proxy server.
Such instructions - to clear cache - cover clearing of cache in the browser, because everybody uses a browser (almost everybody, anyway). Some networks, particularly larger ones, may have a caching proxy server, for both efficiency and security. When you clear your cache in your browser, you won't always think of a local proxy server.

Besides you (or your local network, which you may or may not control) having a caching proxy, there's another possibility. Your ISP may be providing a "Download Accelerator" service. One component of such a service may include a local cache of popular web sites, on your computer, and / or on servers in the ISPs server farm.

You can clear cache in your browser - but not in a caching proxy server.
If you clear the cache in your browser, and there is an upstream cache on your computer, on your network, or on a server at your ISP, the contents of the upstream cache remains undisturbed. When you request a fresh copy of your blog in your browser, and you just cleared cache in your browser, your browser asks upstream for a copy of the blog.

If the blog is in an upstream cache, that's where your browser gets the new copy. Not from the Blogger / Google server.

If you have an upsteam cache, clearing cache will have no effect on problems.
So if there was a problem with your blog, the problem was just solved by Blogger, and you were instructed to clear cache to ensure that you are able to view your blog with the problem resolved - and if you have an upstream cache, your clearing cache in your browser won't do anything to help.

You can, temporarily, bypass cache to diagnose problems.
Here is where, instead of clearing cache, you need to bypass cache temporarily - when you bypass cache, you guarantee a dynamic retrieval from the Blogger / Google server.

This is, unfortunately, a temporary measure - unless you explicitly bypass cache each time, until all upstream caches expire, and each cache explicitly requests a fresh copy of the blog.

Every computer differs - and every different person uses their computer differently.
And here is one of the capricious and random details about web surfing. Every different blogger / blog reader in the world will have a different cache / computer / network infrastructure affecting their surfing activities.

The differences will explain one person responding with
You rock! I'm Following your web site in the future!!
and another
Your advice was useless. Why do you even bother?


Susan said…
You do rock.

Popular posts from this blog

Custom Domain Migration - Managing The Traffic

Your blog depends upon traffic for its success.

Anything that affects the traffic to your blog, such as any change in the URL, affects the success of your blog. Publishing the blog to a custom domain, like renaming the blog, will affect traffic to your blog. The effects of the change will vary from blog to blog, because of the different traffic to every different blog.Followers. People who find your blog because of recommendations by other people.Search engines. Robotic processes which methodically surf your blog, and provide dynamic indexing to people who search for information.Subscribers. People who read your content from their newsfeed reader, such as the dashboard Reading List.Viewers. People who read your content from their browser.No two blogs are the same - and no two blogs will have the same combinations of traffic sources.

Stats Components Are Significant, In Their Own Context

One popular Stats related accessory, which displays pageview information to the public, is the "Popular Posts" gadget.

Popular Posts identifies from 1 to 10 of the most popular posts in the blog, by comparing Stats pageview counts. Optional parts of the display of each post are a snippet of text, and an ever popular thumbnail photo.

Like many Stats features, blog owners have found imaginative uses for "Popular Posts" - and overlook the limitations of the gadget. Both the dynamic nature of Stats, and the timing of the various pageview count recalculations, create confusion, when Popular Posts is examined.