What’s new / Upgrading

This section describes the changes and improvements between different versions of Varnish, and what upgrading between the different versions entail.

Varnish 5.1

• Changes in Varnish 5.1
  • Startup CLI command file
  • Universal VCL return(fail)
  • Progress on HTTP/2 support
  • Hit-For-Pass has returned
  • 304 Not Modified responses after a pass
  • VXID in VSL queries
  • Project tool improvements
  • News for authors of VMODs and Varnish API client applications
• Upgrading to Varnish 5.1
  • varnishd command-line options
  • varnishd parameters
  • Changes to VCL
  • Other changes

Varnish 5.0

• Varnish 5.0 Release Note
  • How to get Varnish 5.0
  • Reasons to upgrade to Varnish 5.0
  • Reasons not to upgrade to Varnish 5.0
  • Next release
  • The obligatory thank-you speech
  • We need more money
  • We also need more manpower
• Changes in Varnish 5.0
  • Separate VCL files and VCL labels
  • Very Experimental HTTP/2 support
  • The Shard Director
  • Hit-For-Pass is now actually Hit-For-Miss
  • Ban Lurker Improvements
  • Request Body sent always / “cacheable POST”
  • ESI and Backend Request Coalescing (“waitinglist”) Improvement
  • Backend PROXY protocol requests
  • Default VCL search path
  • devicedetect.vcl
  • varnishtest
  • misc
  • News for VMOD authors
• Upgrading to Varnish 5.0
  • Changes to VCL
  • Management interface
  • Changes to parameters
  • Other changes

Varnish 4.1

• Changes in Varnish 4.1
  • Proactive security features
  • Warm and cold VCL configurations
  • PROXY protocol support
  • VMOD backends
  • Backend connection timeout
  • Protocol support
  • More modules available
  • Passing data between ESI requests
  • Other noteworthy small changes
• Upgrading to Varnish 4.1
  • Changes to VCL
  • Management interface
  • Runtime users and groups
  • Changes to parameters

Varnish 4.0

• Upgrading to Varnish 4.0
  • Changes to VCL
  • Changes to existing parameters
  • New parameters since 3.0
  • Other changes