WordPress.org

Support

Support » Plugins and Hacks » [Resolved] [Plugin: W3 Total Cache] Gzip already enabled httpd.conf

[Resolved] [Plugin: W3 Total Cache] Gzip already enabled httpd.conf

  • If Gzip is already enabled for all sites via httpd.conf, is there any downside to leaving compression ON in W3TC settings?

Viewing 2 replies - 1 through 2 (of 2 total)
  • It depends if you’re httpd.conf settings are attempting to minify PHP files. Typically that’s not the case and you should be fine otherwise. In general, W3TC will address both cases for you already and you actually don’t have to worry too much about your httpd.conf unless you really want to.

    Thats not the case, thanks. These are the rules I am using:

    <IfModule mod_deflate.c>
    ############################################
    ## enable apache served files compression
    ## http://developer.yahoo.com/performance/rules.html#gzip 
    
     # Insert filter on all content
     SetOutputFilter DEFLATE
     # Insert filter on selected content types only
     AddOutputFilterByType DEFLATE text/html text/plain text/xml text/css text/javascript
    
     # Netscape 4.x has some problems...
     BrowserMatch ^Mozilla/4 gzip-only-text/html
    
     # Netscape 4.06-4.08 have some more problems
     BrowserMatch ^Mozilla/4\.0[678] no-gzip
    
     # MSIE masquerades as Netscape, but it is fine
     BrowserMatch \bMSIE !no-gzip !gzip-only-text/html
    
     # Don't compress images
     SetEnvIfNoCase Request_URI \.(?:gif|jpe?g|png)$ no-gzip dont-vary
    
     # Make sure proxies don't deliver the wrong content
     Header append Vary User-Agent env=!dont-vary
    </IfModule>
Viewing 2 replies - 1 through 2 (of 2 total)
  • The topic ‘[Resolved] [Plugin: W3 Total Cache] Gzip already enabled httpd.conf’ is closed to new replies.