Skip to main content

Your Browser Cache, and Web Sites With Dual Addresses

As you surf the web, and read various web sites, you'll occasionally notice oddities. Following one link, you'll see one version of a web site; following a second link, you'll see the same web page, but with different content.

Obviously, the web page was updated, between the first time that you visited it, and the second time. Nothing odd there.

But here's the oddity. You visit the web site a third time, using the first link, and you see the same, older content. Then you check the second link again, and it shows the newer content again.

What's going on here?

It's simple, really, and this example, which uses Blogger, also applies to the Internet, in general. With Blogger, "" - and "" - both refer to the same blog, which is "bloggerstatusforreal" (and now, "" - but that that is another story altogether).

On your computer, "" and "" are stored in your cache, separately. Let's look at a hypothetical example.
  1. The cache in your browser has a 1 week expiry.
  2. You read

    today. You cache today's copy, under "".
  3. I update "Your Browser Cache, and Web Sites With Dual Addresses" tomorrow.
  4. The following day, you read

    You cache tomorrows copy, under "".
  5. You then reread

    Since it's only 2 days old, you'll read it from cache. The cached copy precedes the update in step 3.

Step 5 will show an older copy of the web page, even though you do it after step 4. Next week, "" will expire a day sooner than "". The problem may repeat, in reverse.

So expect to see alternating differences, one version being more current than the other, forever.

You'll see this problem during the custom domain publication transition, too. In this example, my blog would be alternately visible as "", and "", for instance. This confusion may be even deeper, as you may have more than one cache, affecting your browsing.

If you ask for advice from the experts, and they advise you to clear your cache, this is why. Both versions of the blog, on your computer, will be refreshed simultaneously, and then be in synchronisation with each other. This allows more consistent troubleshooting.

Now you can reduce this confusion by urging your readers to consistently use either the "root" or the "www" alias of the blog. If you're going to effectively cut down on the confusion, though, you'll need to use the Google Webmaster Tools "Preferred domain" setting.

>> Top


GillianWaters said…
what if you have two different addresses hooked to the same dashboard?
Chuck said…
what if you have two different addresses hooked to the same dashboard?

This would be best approached with patience and persistence, as a new discussion in BHF: How Do I?.

Popular posts from this blog

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.

Help! I Can't See My Blog!

I just posted to my blog, so I know that it's there. I can tell others are looking at it. But I can't see it.

Well, the good news is you don't have a blog hijack or other calamity. Your blog is not gone.

Apparently, some ISPs are blocking *, or maybe have network configuration or infrastructure problems. You can access or you can access, but you can't access, or

You can't access them directly, that is. If you can access any free, anonymous proxy servers, though, you may be able to access your blog.

Note: You can use PKBlogs with the URL pre packaged. Here is the address of this post (with gratuitous line breaks to prevent the old post sidebar alignment problem):

And an additional URL, to provide to those suffering from this problem, would be the WordPress version of this post: