This is a compilation of items you need to pay attention to when upgrading from Varnish 2.1 to 3.0
Changes to VCL
==============
In most cases you need to update your VCL since there has been some changes to the syntax.
String concatenation did not have an operator previously, but this has now been changed to ``+``.
``log`` moved to the std vmod
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
``log`` has moved to the std vmod:
log "log something";
becomes
import std;
std.log "log something";
You only need to import std once.
purges are now called bans
~~~~~~~~~~~~~~~~~~~~~~~~~~
``purge()`` and ``purge_url()`` are now respectively ``ban()`` and ``ban_url()``, so you should replace all occurences:
purge("req.url = " req.url);
becomes
ban("req.url = " + req.url);
``purge`` does not take any arguments anymore, but can be used in vcl_hit or vcl_miss to purge the item from the cache, where you would reduce ttl to 0 in Varnish 2.1.
sub vcl_hit {
if (req.request == "PURGE") {
set obj.ttl = 0s;
error 200 "Purged.";
}
}
becomes
sub vcl_hit {
if (req.request == "PURGE") {
purge;
error 200 "Purged.";
}
}
``beresp.cacheable`` is gone
~~~~~~~~~~~~~~~~~~~~~~~~~~~~
``beresp.cacheable`` is gone, and can be replaced with ``beresp.ttl > 0``
returns are now done with the ``return()`` function
The difference in behaviour of ``pass`` in ``vcl_recv`` and
``vcl_fetch`` confused people, so to make it clearer that they are
different, you must now do ``return(hit_for_pass)`` when doing a pass
in ``vcl_fetch``.
Changes to behaviour
====================
Varnish will return an error when headers are too large instead of just ignoring them. If the limits are too low, Varnish will return HTTP 413. You can change the limits by increasing http_req_hdr_len and http_req_size.