Skip to content
varnish master: Collection of Varnish Cache modules (vmods) by Varnish Software
Branch: master
Clone or download
Pull request Compare This branch is 21 commits ahead of varnish:master.
slimhazard Remove vtree.h from EXTRA_DIST.
The dist* make targets had been failing, now passing.
Latest commit e94923f Apr 17, 2019
Type Name Latest commit message Commit time
Failed to load latest commit information.
docs update docs Mar 26, 2019
m4 Use autoconf macros shipped with Varnish 4.1.4+ Dec 19, 2016
man Revert "Build man pages from src/vmod_*.vcc files" Apr 25, 2016
src Remove vtree.h from EXTRA_DIST. Apr 18, 2019
.gitignore Use autoconf macros shipped with Varnish 4.1.4+ Dec 19, 2016
.travis.yml Update Varnish installation for Travis CI builds Nov 10, 2017
AUTHORS Squashed import from development repository. Mar 4, 2016
CHANGES.rst Bump version number May 15, 2018
COPYING Add license to source files. Apr 8, 2016
LICENSE Squashed import from development repository. Mar 4, 2016 Revert "AM_EXTRA_RECURSIVE_TARGET seems to act on distcheck" Dec 19, 2016
README.rst a word about this repo Apr 15, 2019
bootstrap Bump automake requirement to 1.12.2 Oct 30, 2018
test-vclsnippet Automate test runs. Jul 12, 2016


Status of this repository

This repository is based upon with necessary adjustments for varnish-cache master. It is being maintained by

Varnish module collection by Varnish Software

This is a collection of modules ("vmods") extending Varnish VCL used for describing HTTP request/response policies with additional capabilities.


  • Simpler handling of HTTP cookies
  • Variable support
  • Request and bandwidth throttling
  • Modify and change complex HTTP headers
  • 3.0-style saint mode,
  • Advanced cache invalidations, and more.
  • Client request body access

This collection contains the following vmods (previously kept individually): cookie, vsthrottle, header, saintmode, softpurge, tcp, var, xkey, bodyaccess

Supported Varnish version is described in the CHANGES.rst file. Normally this is the last public Varnish Cache release. See PORTING below for information on support for other versions of Varnish.


Source releases can be downloaded from:

Installation requires an installed version of Varnish Cache, including the development files. Requirements can be found in the Varnish documentation.

Source code is built with autotools, you need to install the correct development packages first. If you are using the official Varnish Project packages:

sudo apt-get install varnish-dev || sudo yum install varnish-devel

If you are using the distro provided packages:

sudo apt-get install libvarnishapi-dev || sudo yum install varnish-libs-devel

Then proceed to the configure and build:

make check   # optional
sudo make install

The resulting loadable modules (libvmod_*.so files) will be installed to the Varnish module directory. (default /usr/lib/varnish/vmods/)


Each module has a different set of functions and usage, described in separate documents in docs/. For completeness, here is a snippet from docs/cookie.rst:

import cookie;

sub vcl_recv {
        set req.http.cookie = cookie.get_string();
        # Only SESSIONID and PHPSESSID are left in req.http.cookie at this point.


The source git tree lives on Github:

All source code is placed in the master git branch. Pull requests and issue reporting are appreciated.

Unlike building from releases, you need to first bootstrap the build system when you work from git:

make check # recommended

If the configure step succeeds but the make step fails, check for warnings in the ./configure output or the config.log file. You may be missing bootstrap dependencies not required by release archives.


We encourage porting of the module package to other versions of Varnish Cache.


The goals of this collection are:

  • Simplify access to vmod code for Varnish users. One package to install, not 6.
  • Decrease the maintenance cost that comes with having 10 different git repositories, each with autotools and (previously) distribution packaging files.

Expressed non-goals are:

  • Import vmods that require external libraries, like curl or geoip. This collection should be simple and maintenance free to run.
  • Support older releases of Varnish Cache.
  • Include every vmod under the sun. We'll add the important ones.

Addition of further vmods is decided on a case-by-case basis. Code quality and maintenance requirements will be important in this decision.


This code is maintained by Varnish Software. (

Issues can be reported via the Github issue tracker.

Other inquires can be sent to

You can’t perform that action at this time.