Hello,

I have been using Boost successfuly in other Drupal sites, but I am wondering if Boost is doing things correctly.

Scenario:

Latest Boost dev installed
Firefox 3.x, IE8 and latest Chrome.
Boost correctly displays the timestamp at the bottom of the page
Settings page edited to add the base_url
HTTP Headers send no-cache, no-store, must-revalidate
Added pragma no-cache at the bottom of the page inside tags as Microsoft suggested.
Poormanscron configured at every 20mins, Boost at 30mins

Issue:
Page still shows the last timestamp (even if way passed the expire date) at the bottom when I press F5 or the refresh button on each browser. Cron also ran correctly way after the expire date.

Then I send CTRL-F5 with firefox or Chrome, page refreshes correctly with the new boost delivered content.
After that I press regular F5 or press refresh button and all other browsers and now present the latest content.

I tried doing the CTRL-F5 using a virtual machine and after it delivered the fresh content, all the browsers in my host machine also delivered the new content with a regular refresh.

Shouldn't Boost delivered new content if available with a regular refresh?

Comments

tonydevel’s picture

tonydevel commented
Assigned: tonydevel » Unassigned
tonydevel’s picture

tonydevel commented

I just forced the renewal of the expiration by calling boost_cache_clear_all() from another module at cron run. It seems to work, but I would like to know the potential threats by doing this.

mikeytown2’s picture

mikeytown2 commented

There is an option to not flush the caches on cron if the site has not changed. I use it for smaller sites.

"Check database timestamps for any site changes. Only if there has been a change will boost flush the expired content on cron." its under "Boost cache expiration/flush settings"

tonydevel’s picture

tonydevel commented

I have that setting checked, the feeds I have configured through Aggregator should have changed the database timestamps though.

As a test I'm gonna try unchecking that option, removing the boost_cache_clear_all() call and see how it goes.

tonydevel’s picture

tonydevel commented

Test didn't work, CTRL-F5 was the only way to refresh the content.

mikeytown2’s picture

mikeytown2 commented

Does your browser support mod_headers? What is the etags settings for boost? Try setting the etags to "Set FileETag 'MTime Size' - Useful in server clusters (Recommended)" under Boost Apache .htaccess settings generation.

The etag settings is a one liner

FileETag MTime Size

Place in your .htaccess file in the cache dir; if the cache dir etag doesn't exist then place in the web root .htaccess file.

7.x issue for this
#1070232: Rely on etags for cache staleness

BTW yslow likes this ETag setting if your worried about that.

tonydevel’s picture

tonydevel commented

Yes! it worked!

tonydevel’s picture

tonydevel commented

Just for the record, it was injected into the .htaccess in the cache folder.