Just installed beta2 and boy that looks like alot of work. Thanks.

I see that gzipping is one combined switch that controls both Boost and Core. What if I want Boost to create gzipped static files, but I want to allow my webserver to handle all the gzipping of non-cached files, logged in users, css, js, etc?

Comments

mikeytown2’s picture

mikeytown2 commented

Anything that hits drupal (index.php) will not be sent compressed, unless it is in the database cache. Core's database cache only serves content to anonymous users. Boost grabs the filenames of CSS/JS files located in the pages it caches. Be much more specific and I should be able to give you a clearer answer, as your webserver should be handling the gzipping of stuff boost doesn't.

brianmercer’s picture

brianmercer commented

Without the Boost module loaded, there is an option on the core Performance page that says

"Page compression: By default, Drupal compresses the pages it caches in order to save bandwidth and improve download times. This option should be disabled when using a webserver that performs compression."

My understanding is that Drupal will compress pages for you, but it is faster and more efficient to let your web server do the compression, thus the recommendation to turn off that compression if your webserver is set up to do it.

So I'd like that core option off, but the Boost option to create static precompressed files to be on.

Unless I'm misunderstanding the core setting.

mikeytown2’s picture

mikeytown2 commented

Key phrase

Drupal compresses the pages it caches

brianmercer’s picture

brianmercer commented

I think I get it now. Thanks.

mikeytown2’s picture

mikeytown2 commented
Status: Active » Fixed

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.