If I using Google Chrome, and when I enabled the Boost module, the guests only see blank pages in many cases. Refreshing the page with F5 resolves the problem, but can not be expected to refresh on each page, when the guests visiting the pages first time. The Boost setup is the default, and "view source" is works fine in Chrome. Just the normal view is a blank screen.

Comments

vasike’s picture

vasike
Location Ramnicu Valcea
CreditAttribution: vasike commented

subscribe

aze2010’s picture

aze2010 CreditAttribution: aze2010 commented

subscribing

1. Every Cache completly cleared
2. Activate Boost
3. With Chrome surfing my homepage (no cache since now)
4. The Page (non cached) gets white (no display)
5. After Refresh (Cache is generated from first visit with the white/blank page)
6. Chrome now display the page

This only happen in Chrome and when there is no cached-version.
If there is a cached (boost) cached version, chrome works like any other browser.

What can it be?

Many regards
Alex

Anonymous’s picture

Anonymous (not verified) CreditAttribution: Anonymous commented

If you go into Chrome and use Tools > Developer tools until you get a white page (unfortunately you have to turn it on on the site so you may get a page display because of the reload).

  • Choose Network
  • Then scroll to the top of the page in the developer window.
  • Select your page
  • It will bring up to the right tabs labelled: "header', "previews", "response",

Under the headers tab (you may have to scroll down past the "request"), what is the response header for a blank page ? and in "response" (without reloading) do you have nothing ?

It could possibly be that chrome is not interpreting the cached page as text/html, are your pages zipped ? in the response headers it could have content-encoding to tell chrome.

bgm’s picture

bgm CreditAttribution: bgm commented
Category: bug » support

Can you check in your .htaccess to make sure that it has:

Header set Cache-Control "no-store, no-cache, must-revalidate, post-check=0, pre-check=0"

Chrome tends to be very aggressive on caching and if "no-store" is not there, it will cache anyway.
Although there is probably another issue with gzip causing the cache to be invalid for some reason.

budgetstockphoto’s picture

budgetstockphoto CreditAttribution: budgetstockphoto commented

I have the exact same issue with boost 6.x-1.18 on drupal core 6.28

i've come to the conclusion this is likely to be platform related, ive got the same boost drupal configuration at a different cpanel host and all is fine. Ive spent an hour or so playing about disabling deflate, poking at various stuff and I'm at a loss.

Interestingly although chrome displays the white screen if you press ctrl-u the source is displayed, I'm trying this on a page that boost is not caching (firebug says the page is response 200, but Status column shows (failed), but in the network tab it then proceeds to download the css files and js included in the header of the 'failed page' so it must be loading the page (?)


Request Method:GET
Status Code:200 OK
Request Headersview source
Accept:text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8
Accept-Charset:ISO-8859-1,utf-8;q=0.7,*;q=0.3
Accept-Encoding:gzip,deflate,sdch
Accept-Language:en-US,en;q=0.8
Cache-Control:no-cache
Connection:keep-alive
Pragma:no-cache
User-Agent:Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/537.22 (KHTML, like Gecko) Chrome/25.0.1364.152 Safari/537.22
Response Headers
Cache-Control:must-revalidate
Connection:close
Content-Encoding:gzip
Content-Length:30421
Content-Type:text/html; charset=utf-8
Date:Mon, 11 Mar 2013 06:20:06 GMT
Expires:Sun, 19 Nov 1978 05:00:00 GMT
Last-Modified:Mon, 11 Mar 2013 06:20:07 GMT
Server:Apache/2.2.9 (Debian)
Vary:Accept-Encoding
X-Powered-By:PHP/5.2.6-1+lenny9

I'm thinking that my somewhat out of date debian might be to blame?

I'm also somewhat puzzled by what exactly is gzipping this page, i've disabled all of the gzip options in "performance". The site where I don't see this issue has the same config and it does not return a "Content-Encoding:gzip" for a 'first page load" (i.e. an uncashed page).

Anonymous’s picture

Anonymous (not verified) CreditAttribution: Anonymous commented

Almost certainly it''s the zipping and when gzip was placed into the 7.x dev tree it had to be removed because it was removing a few bytes from the page output, #1416214-14: Basic gzip support for 7x the difference in configurations were for mod_mime and also using the Forcetype .htaccess directive, so it is very "installation" specific rather than "distribution" specific.

What is probably gzipping your page is mod_deflate or mod_gzip in the virtual host configuration, YMMV, in general chrome is particularly sensitive to badly gzipped files and displays nothing whereas firefox does better but can display garbage. It's almost impossible to debug as the compressed output is never visible, being decompressed immediately by the browser. You could compare .gz page sizes with the page on server and the size of output in firebug, and check the config of apache modules if you have root access using

apachectl -t -D DUMP_MODULES

In your cache you should remove any .gz file and you'll probably find that there is a difference. You might also want to check that the .htaccess has been updated after you've turned off all the gzip options to rule boost out of the equation.