Varnish HTTP Cache

I’m new here, please explain this Varnish thing

Questions and Answers

What is happening


Varnish Cache 5.0.0 has been released! /Lasse /phk


(And yes, we’re dog-food running it on the site)


In varnish 5.0 it will be possible to use separate VCL files for different kinds of requests, for instance one VCL file per Host: domain.

You can test it already now in the trunk version.

Read more about separate VCL files here


If you are running Varnish, protecting against the HTTPOXY CGI vulnerability is a simple as:

sub vcl_recv {
        unset req.http.proxy;


Varnish Cache 4.1.3 has been released! /Lasse


Varnish Cache 4.1.3-beta2 is out. Most likely this will become 4.1.3 final. Source and packages in Releases & Downloads. /Lasse


VarnishCon Europe 2016

Don’t miss it next time.


Varnish Cache 4.1.3-beta1 is released just in time for VarnishCon 2016. Please give it a go if you can. See Releases & Downloads /Lasse


If you are interested, here is an outline of the projects new IT infrastructure. /phk


Sorry if it looks a bit sparse around here, we’re in the process of moving the Varnish Cache project to its own infrastructure.

If you want to help out, we will gladly take pull requests to the new homepage, you can find it in this github repos. /phk


You can access the varnish-cache homepages with HTTP or HTTPS as you like.

We save the logfiles from our Varnish instance for a limited period, in order to be able to debug problems.

The old homepage ran Google Analytics, and we have continued that here for now, but unless we actually learn something useful from the data they collect, it will be discontinued.