By fkdsfodsf on
I am designing a site for people in the developing world.
For some reason, my site breaks when I turn on BOTH drupal's cache and gzip.
Considering I can only turn one on (unless someone knows a way to fix this), which one provides the biggest benefit to load speed?
Comments
Logged on or not?
If the majority of your users will not be logged on, use cache, if they will be logged on use gzip.
Sami
--
Read the handbook, search the forums, then ask!
http://drupal.etopian.net (Consulting, Development, and Hosting)
Just wondering, how are you
Just wondering, how are you turning on the gzip ?
http://01debug.com
Through HTACCESS
I'm turning it on through my .htaccess file:
php_flag zlib.output_compression on
php_value zlib.output_compression_level 1
There have been problems
There have been problems with zlib.output_compression. For some reason this does not check the sent headers (which clearly say that the output is already gzipped). This has never happened with mod_gzip, though, so you might want to try this.
--
Drupal services
My Drupal services
--
Drupal services
My Drupal services
how would I turn mod-gzip
how would I turn mod-gzip on?
mod_gzip
Get it here: http://sourceforge.net/projects/mod-gzip/
Configure, make etc, then put it with your other apache modules
Add the line to load the module in httpd.conf (put it last the docs said)
I used the default config provided and put it in an htaccess file where I wanted to test it.
Restart apache.
Check a page here to see if it's working
http://leknor.com/code/gziped.php
* Most pages I checked showed about 75% compression. Pretty cool.
is this related
a long time ago I had the same, both drupal and apache were compressing pages resulting in a gzipped gzipped html page which was unzipped once at the client rendering garbage. see what I did and if this solved the problem and please add your name and config to that bug report as well.
--
groets
bertb
--
groets
bert boerland
Solution for 4.6 users
I had the same problem with my 4.6 website, and finally found the solution in this thread. The solution is to change the data type of the "data" column in the "cache" table from "longtext" to "longblob". The above referenced node discusses changing the data type to "mediumblob", but I looked at the 4.7 table definition (where this issue seems to have been resolved), and they used "longblob". After changing the data type and clearing the cache table, voila! Caching finally works!
Steve
Revista Y AHORA QUÉ | Selectividad - Universidades - Foro Blog Chat Estudiantes
Steve
Revista Y AHORA QUÉ | Selectividad - Universidades - Foro Blog Chat Estudiantes