Hi,
My site's problem is when people access the primary domain name (Homepage url), the site can not be accessed but there is a tiny .gz file download instead. Ip address is no problem to access, url/index.php can open homepage and all the internal link can be opened property eg:url/user, url/register,etc. I strongly suspect it causes by boost module. Coz that .gz file can be opened and actually it is the homepage's html file with " Page cached by Boost @ 2012-12-07 13:44:46, expires @ 2012-12-07 14:44:46 " at the bottom. Obviously, this is an expired boost cache. This problem is quite similar with the issue in wordpress

But I had try to remove all the boost module, remove the code in .htaccess and clear all the cache, run cron, delete all the cache folder. disable all the page compression, the problem still there. It really makes me crazy.

After I did all process above. I access through IP address and found there is not Page cached by Boost in homepage now. But use url to access website there is still get a .gz file with "page cached by boost @xxxx".

Where is that .gz file come from and how can I solve this problem. And I found not all the users have this problem.

Thank you in advance.

ps: I had try this method:http://drupal.org/node/1008534But it seems useless in my site :-(

CommentFileSizeAuthor
2 copy.jpg277.7 KBssiufoo
Support from Acquia helps fund testing for Drupal Acquia logo

Comments

ssiufoo’s picture

Issue summary: View changes

.

bgm’s picture

Is the boost "aggressive gzip" option enabled? If yes, can you test with that option disabled?

Might be related to #707500: Aggressive gzip: boost-gzip-cookie-test.html not found in log

You can also disable gzip compression completely, and flush cache to delete the .gz files in your "cache" directory. Apache will take care of compression otherwise (slight overhead, but unless you have a very busy site, it won't make a huge difference).

ssiufoo’s picture

Hi bgm,

Thanks for you help. I am sure I had made aggressive gzip option disable. I had stop boost module and delete cache folder few days. Till today morning, miracle occurred. It seems auto-fixed. This problem still weird. But I am sure a method can fix it: upgrade drupal core. (replace all the file and put old sites in new core file.)

ssiufoo’s picture

Issue summary: View changes

..