Adds varnish integration to TYPO3

Installs: 8 990

Dependents: 0

Suggesters: 0

Security: 0

Stars: 2

Watchers: 4

Forks: 0

Open Issues: 1


5.0.0 2023-07-31 18:53 UTC

This package is auto-updated.

Last update: 2024-05-10 09:16:51 UTC


stability-stable TYPO3 V12 Minimum PHP Version GitHub CI status

Adds varnish integration to TYPO3. Ensures varnish caches are flushed when TYPO3 caches are flushed. Uses cache tags to flush all necessary content.


The current version (5.x) of this extension has been tested using these versions:

  • TYPO3 12.4 on PHP 8.1
  • TYPO3 12.4 on PHP 8.2


Install the package via composer.

composer require netlogix/nxvarnish



This extension provides some configuration in Install Tool.

  • varnishHost: required, needed to communicate with Varnish in order to purge caches
  • allowCacheLogin: optional, send normal cache headers even when someone is logged in


Varnish needs some special configuration to understand cache tags and BAN requests. Add this to your Varnish .vcl:

# WARNING: this is an example how to add tag-based purging to an existing
# Varnish configuration. This is *not* a complete configuration!

# a list of clients that are allowed to initiate a BAN
acl purge {
      # add whatever IPs are allowed to initiate a BAN
      ""/16; # just an example

sub vcl_recv {

    # ...

    if (req.method == "BAN") {
        # only allow cache BANs from known IPs
        if (!std.ip(req.http.X-Client-Ip, client.ip) ~ purge) {
            return (synth(405, "Not allowed."));

        # ban using cache tags
        if (req.http.X-Cache-Tags) {
            # this will ban all cache objects with matching tags
            ban("obj.http.X-Cache-Tags ~ " + req.http.X-Cache-Tags);

            # create an HTTP 200 response and exit
            return (synth(200, "Ban added."));

        # return an error if no cache tags were provided.
        # you might need to remove this if you have additional BAN conditions
        return (synth(400, "Bad Request."));


    # ...


sub vcl_deliver {
    # ...

    # remove cache-tags header from response sent to client
    unset resp.http.X-Cache-Tags;

    # ...