Varnish HTTP Cache

I’m new here, please explain this Varnish thing

Questions and Answers

What is happening

2016-09-27 - Send us (more) money!

If we want to keep up the same activity level as the last couple of years, we need €2000/month to buy more of Poul-Hennings time.

So if Varnish improves your company’s profit, please invest in a one-time or recurring Varnish Moral License to help fund the projects future.

Thanks in advance!

And a big thanks to the companies already sponsoring Varnish:

  • Fastly
  • Varnish-Software
  • [your companys name could have been here...]

2016-09-15 - Varnish 5.0

Varnish Cache 5.0.0 has been released! /Lasse /phk


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

2016-08-16 - Separate VCL files

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

2016-07-18 - HTTPOXY workaround

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

sub vcl_recv {
        unset req.http.proxy;

2016-07-06 - Varnish 4.1.3

Varnish Cache 4.1.3 has been released! /Lasse


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.