I have an issue similar to the one described here: http://drupal.org/node/1875578

Client running a high traffic (~10,000 page views per day) blog. Posts are created and scheduled to publish at the top of each hour from 6 pm to 9 am. there are 16 posts altogether, and they are presented and promoted to the front page.

I checked in the morning and the front page is presenting different results depending on the browser. It presents correctly in Chrome, presents accurately in Opera, but shows the posts only through 12 am on Firefox.

I have tried the routines proposed in the link above (unchecked the "ignore cache flush" command and then flushing the cache, flushing the cache on Firefox several times, and it has not worked.

What I just noticed, while writing this post, is that Boost is caching two URLs: one with prefix 'www' and one without. The one without the 'www' prefix is clearing; the one with the www prefix is NOT clearing.

Why is it caching both? Do I need to change the redirect in the .htaccess file?

Help!

Comments

Anonymous’s picture

Anonymous (not verified) commented
Priority: Major » Minor

At the moment this is not boost, but basic drupal .htaccess configuration

  # If your site can be accessed both with and without the 'www.' prefix, you
  # can use one of the following settings to redirect users to your preferred
  # URL, either WITH or WITHOUT the 'www.' prefix. Choose ONLY one option:
  #
  # To redirect all users to access the site WITH the 'www.' prefix,
  # (http://example.com/... will be redirected to http://www.example.com/...)
  # uncomment the following:
  # RewriteCond %{HTTP_HOST} !^www\. [NC]
  # RewriteRule ^ http://www.%{HTTP_HOST}%{REQUEST_URI} [L,R=301]
  #
  # To redirect all users to access the site WITHOUT the 'www.' prefix,
  # (http://www.example.com/... will be redirected to http://example.com/...)
  # uncomment the following:
  # RewriteCond %{HTTP_HOST} ^www\.(.+)$ [NC]
  # RewriteRule ^ http://%1%{REQUEST_URI} [L,R=301]

DIfferent browsers behaving differently can be due to all kinds of things from being logged in when boost only serves anonymous pages, so you need to check the html source for the boost comment, through to your browser caching and requiring a hard reload light shift+command+R, and could be your apache configuration.

To investigate, use firefox and firebug. And check the response headers of the PHP page to check that it is sending out no-cache.

RKopacz’s picture

RKopacz commented

Thanks for the quick feedback. I did actually enable that redirect in .htaccess, after posting that comment, but it seems like the caching for www persists.

I have two subdirectories in the cache/normal directory:

example.com, and
www.example.com

Since I have enabled the redirect in .htaccess, do you think it would be OK to simply delete this directory, without consequence? Maybe regenerate the boost htaccess code and reinsert before that?

Incidentally, we were having serious server daily crashes since launch of the site in question do high CPU load. Boost has taken the edge off, no crash today, so thank you to all for the fine work on the module :)!

Anonymous’s picture

Anonymous (not verified) commented

Delete the directory, if the redirect is not working then it will just be regenerated as will the .htaccess file within.

Have you confirmed the headers and the boost comment in the browsers ?