Does not purge compressed Objects in Varnish 2.0

That should be safe to add in. Let me check with my cohort to make sure ??

Are you using this with another caching plugin perchance?

Followup, what if you changed the function to this:

protected function purgeUrl($url)
    {
        wp_remote_request($url, array('method' => 'PURGE', 'headers' => 'Accept-Encoding: *'));
    }

Does that work?

This might be different if you set up the compression in the VCL with Varnish 3.0. However, without having this in the VCL I suspect that the problem is the same.

Without havign which? I want to make sure I cover this in the FAQ too ?? Normally the answer would be “Well make sure your VCL knows to purge those!” but I think this is one of those fundamental differences between v2 and v3 and how it handles partial pagenames.

Thanks a lot for you answer! Properbly my intention was not clear. The code I put into my post is working completly fine ?? I wanted to thank you for the plugin by contributing somthing that might help others as well.

I did not try your change (because everything is running fine). However, as I just wrote the VSS-File I can still remember this part from my /etc/varnish/default.vcl:

if (req.http.Accept-Encoding) {
  if (req.url ~ "\.(jpg|png|gif|gz|tgz|bz2|tbz|mp3|ogg)$") {
    # No point in compressing these
    remove req.http.Accept-Encoding;
  } elsif (req.http.Accept-Encoding ~ "gzip") {
    set req.http.Accept-Encoding = "gzip";
  } elsif (req.http.Accept-Encoding ~ "deflate" && req.http.user-agent !~ "MSIE") {
    set req.http.Accept-Encoding = "deflate";
  } else {
    # unkown algorithm
    remove req.http.Accept-Encoding;
  }
}

This might be different if you use a smarter VSS or use compression inside Varnish. But I am relativly sure it won’t work for me. Thanks once more for the great plugin!

While the code you gave does work, I didn’t want to add in multiple purge requests in order to keep the CPU and memory footprint as small as possible (very important in caching), so I wanted to see if one line would do.

Varnish 2 is not something the original plugin had planned to support, and I don’t actually have it to test on. Also in general you don’t have gzip files in WP called directly, so it’s just a little odd from my perspective. That’s why I’m trying to figure out how you set things up ??

While the code you gave does work, I didn’t want to add in multiple purge requests in order to keep the CPU and memory footprint as small as possible (very important in caching), so I wanted to see if one line would do.

I see your point. But if you look into the VSS you can see that this line cannot work (unless I change the VSS). I do not know how to purge more that on object with one call in a VSS (I am happy if somebody explains me, then I change my VSS).

Also in general you don’t have gzip files in WP called directly, so it’s just a little odd from my perspective. That’s why I’m trying to figure out how you set things up ??

From my perspective as well ?? It might be due to the cache-warmup that I do with wget and an explicit “Accept-Encoding: gzip”. Before I did that my Varnish send out an uncompressed version of the html-files. However, I think this might not be a problem for Varnish 3 as it has a more sophisticated handling of compression.

For the moment I am very happy with your extension and my hack. But if you tell me how to change the VSS I am also happy to try it. Thanks once more for the great Extension!

I wrote VSS all the time but I meant VCL. Sorry about that.