Comments on: Making WP-Super-Cache gzip compression work

By: WP Super Cache – The Ultimate WordPress Caching Plugin | All My Brain

WP Super Cache – The Ultimate WordPress Caching Plugin | All My Brain — Sat, 16 Jan 2010 14:08:08 +0000

[...] I posted an update that deals with getting the super cache compression to [...]

By: Dennis

Dennis — Sat, 16 Aug 2008 00:39:57 +0000

Install FireBug (Plugin) and see what headers are being returned. You can use Telnet to debug the raw information returned too.

By: Buck

Buck — Fri, 15 Aug 2008 22:44:30 +0000

Recently moved servers from StartLogic to HostGator. Having a problem with WP-Cache. I know how to set it up. I know about permissions. It just would not work on HostGator (even though others have it working).
Then I found SuperCache and decided to try it. Funny. SuperCache works for IE. And for FireFox- on my other machines, but not my Toshiba laptop. I just completely removed Firefox and reinstalled – same thing.
Any ideas?

By: error12

error12 — Fri, 01 Aug 2008 10:16:21 +0000

Oh, it’s solved now. Litespeed compresses the files anyway.

By: error12

error12 — Thu, 31 Jul 2008 21:34:19 +0000

Hi! It does not work on Litespeed servers

I geuess the suspect is:
AddType text/html .gz

as the pages are rendered as garbage text under IE. Such a pitty, unless there is a solution.

By: Dennis

Dennis — Sat, 12 Jul 2008 19:40:42 +0000

Best I can recommend is using telnet to grab your web page and examine the exact headers that are being sent/received. Or you could try tcpdump or something. You’ll have to determine which header is missing or incorrect.

By: Rishi Kumar

Rishi Kumar — Fri, 11 Jul 2008 22:47:14 +0000

Hi Dennis, I’m having some trouble buddy. I’m able to run Super-Cache properly (as long as GZip is not enabled) on IE6 and IE7; however, once it’s enabled, it asks me to download the page. I tried following your aforementioned code, but it results in the website not even loading on IE6/7. I pasted the “” code in my /cache/.htaccess folder and the “

By: Richard X. Thripp

Richard X. Thripp — Mon, 23 Jun 2008 01:02:29 +0000

Thanks, did the same thing on my blog. Firefox figures out the page is HTML despite the gzip HTTP header, but Internet Explorer gets confused and prompts you to download the site. The .htaccess file in the cache directory fixes the headers.

By: bushtool

bushtool — Sun, 27 Jan 2008 22:14:34 +0000

Super cache compression is working. Wp-cache is caching files and storing them in the cache directory. The only files being cached according to the listing is feeds and print files.

Anyone know why the other page loads are not being cached. There is no indicator at the bottom of the source file about wp-cache, just compression even when reloaded.

Thanks for the help

By: Dennis

Dennis — Fri, 09 Nov 2007 16:25:07 +0000

Never mind Donncha, saw your post on the WordPress plugin page about the changes being in trunk.

I think the development version is right on! Thanks.

By: Dennis

Dennis — Fri, 09 Nov 2007 16:03:03 +0000

Did you mean update to a new plugin version? I still see 0.3.1 as the latest. If I change the wp- in the current version will it break?

By: Donncha O Caoimh

Donncha O Caoimh — Fri, 09 Nov 2007 14:44:27 +0000

Update your plugin and change the “wp-” to “wp-.*.php”
It now uses preg_match instead to match strings

By: Dennis

Dennis — Fri, 09 Nov 2007 14:24:59 +0000

I found out why my last two posts weren’t being cached. They had wp- in the URL, which is a rejected URL string on the cache options. I changed the slug in the post to wp_ instead for that part and it fixed the problem.

It is sort of ironic to have a post about wp-super-cache not being cached isn’t it.

By: Dennis

Dennis — Fri, 09 Nov 2007 14:08:11 +0000

Unfortunately, you have to put it in your vhosts.conf (or httpd.conf depending on your setup) if you want to use the Location element. You can Add the AddEncoding and AddType headers to their own .htaccess file in the /wp-content/cache/supercache directory though. I haven’t actually tried this but it seems like it ought to work.

By: Baz L

Baz L — Fri, 09 Nov 2007 14:02:27 +0000

Just checking,

This goes in the .htaccess file right?

By: Dennis

Dennis — Fri, 09 Nov 2007 12:56:12 +0000

Actually, now that you pointed it out, I double checked the contents of my super cache directory. I’ve noticed the index page and a few posts are cached (and have gz copies) but this post, and a number of others do not have a cached copy. I noticed that after I made these comments, the cached copy of the index page was regenerated (to show the correct comment count), but still, there is no updated cached copy for this post. I’m going to try deleting the cache, and seeing what gets regenerated.

Sure enough. After deleting the cache, the index page, meta pages (tags, categories) and a lot of older posts are getting put back into the cache. These latests two posts about wp-cache are not being stuck back in the cache though. I have no idea why this is. I’m on version 0.3.1 of WP-Super-Cache.

By: Dennis

Dennis — Fri, 09 Nov 2007 12:32:01 +0000

Hey Donncha, I still have the plugin enabled. I get the gzipped response when I telnet to port 80 and create a request with Accept-Encoding: gzip as one of the headers. You might try a different browser and look at the source. That’s how I tested it mostly since when you’re logged in you don’t get the super cache pages.

By: Archon810

Archon810 — Fri, 09 Nov 2007 08:59:43 +0000

I put the Location into vhosts.conf. It works if you have access to apache configuration files, but I’m not sure where you would put it otherwise…

By: Donncha O Caoimh

Donncha O Caoimh — Fri, 09 Nov 2007 08:44:10 +0000

Oh yeah, did you disable the plugin? I don’t see the caching string at the end of this page, even before I left a comment.

By: Donncha O Caoimh

Donncha O Caoimh — Fri, 09 Nov 2007 08:43:28 +0000

I actually came up with the same solution but with an extra .htaccess file in the cache folder before my initial release of the plugin, but at the time feeds were cached and the compressed feeds weren’t playing nicely with Feedburner.
That’s all changed now as feeds aren’t cached so I can fix it again. Thanks!
Location can’t be used in a .htaccess, so I’ll probably have to create that file in the cache folder again.