Www vs non-www caching differences

#1

I’m suspecting this is a caching question.

I get a different (older) version of my website when I enter www.wmbc.ca as opposed to wmbc.ca.

It appears that they have different caching criteria, but should be the same.

Nothing obvious jumps out at me in the settings for comet cache.

Can you advise?

#2

In WordPress’s General Settings, what do you have set for:

  • WordPress Address (URL)

  • Site Address (URL)

#3

Thanks for the quick reply.

Both are set the same.

http://wmbc.ca

#4

Well, that’s good, but then something else on your site probably isn’t configured correctly. You really want http://www.wmbc.ca automatically redirecting to http://wmbc.ca When that’s working, Comet Cache should work fine.

The first thing I’d try is clearing the cache. But you’ve probably already done that.

The next thing would be to see what’s in your site’s .htaccess file or ask your host how to get everything pointing to http://wmbc.ca

#5

Yup, I’ve done all 3

  1. Cleared the cache, no change (odd, would have thought that would have
    worked).
  2. Checked htaccess. Only reference to wmbc is in the following code,
    which I’m not sure means

    • Reduce Comment Spam - Security > Settings > System Tweaks >

    Comment Spam
    • RewriteCond %{REQUEST_METHOD} POST
    • RewriteCond %{REQUEST_URI} /wp-comments-post.php$
    • RewriteCond %{HTTP_USER_AGENT} ^$ [OR]
    • RewriteCond %{HTTP_REFERER}
      !^https?://(([^/]+.)?wmbc.ca|jetpack.wordpress.com/jetpack-comment)(/|$)
      [NC]
    • RewriteRule ^.* - [F]
    1. Fired a question off to hosting company. Waiting for a response.
#6

Response from provider.

Both domains are pointing to the same IP address. Can you disable the
cache setting ?

I disabled cache and now both addresses return same content. Not sure why
clearing the cache did not produce the same result, unless I did
incorrectly.

I can ask for a re-direct but wondering if Comet Cache shouldn’t treat both
addresses the same?

#7

I think Comet Cache will cache only what you have in the two settings I asked about, because that’s effectively what those settings are telling it. It doesn’t know about the www variant because there’s nothing to tell it that it exists.

If you have the Pro version, you could use a sitemap plugin to create a sitemap and then turn on Comet Cache’s Auto-Cache engine. This would enable you to include whatever you want in the sitemap.

Otherwise, since you have chosen those settings, there’s simply no reason to have the www variant accessible and you should definitely have a redirect in place.

#8

OK, thanks for the explanation. Provider has said they’ve redirected one to
the other, so should be good.

Thanks again for quick response!