Skip to end of metadata
Go to start of metadata


  • Setup the Drupal site on admin/config/development/performance. Set your cache lifetimes.
  • Set the reverse proxy settings found in settings.php.

default.vcl (Varnish 3 only)

  • No labels


  1. Anonymous

    Might be a Varnish version thing but I found I couldn't use;

    set req.http.Cookie = ";" + req.http.Cookie;

    and had to change it to this instead;

    set req.http.Cookie = ";" req.http.Cookie;

    (and the same for the one around div class "error")

    1. Yes, that's because you're still using Varnish 2. I've updated the page titles to better reflect that this is Varnish 3. All the changes between the two versions are here:


  2. Anonymous


    I've installed default varnish and changed default.vcl as per your post.

    Varnish is up and running.

    I also installed varnish module and amended settings.php as per module's README.txt instructions.

    I also setup cache lifetimes on admin/config/development/performance

    On varnish module's settings page it says 'Varnish is running' however I do not get any Varnish headers to indicate that pages are served by it.

    Am I missing something?

  3. You sure you're hitting the right port? Varnish needs to be configured to listen on port 80, and then use Apache as a backend on 8080.


  4. Anonymous

    Error 503 Service Unavailable

    Service Unavailable

    Guru Meditation:

    XID: 53417928

    Varnish cache server

    why is this?

    1. Anonymous

      I had the server down, but still when navigating into the admin/config/development/varnish, I get

      The Varnish control terminal is not responding at on port 8080 although I have started varnish sudo varnishd -a -b -s file,/tmp,500M

      I can still navigate the site using localhost:8080

      1. Anonymous

        The control terminal's port shouldn't be the same as the port varnish is listening for traffic on.

        6082 is the default.

        Your application also needs to use varnish's secret key to exchange information with the control terminal.

        You can copy the key from /etc/varnish/secret and update the Varnish secret in the varnish module's configuration page in your site.

  5. Anonymous

    Thanks for quick reply.

    I am using port 80 in apache and listening varnish on 8080 though I can't find the secret file or /etc/varnish directory.

    I did $ find / -name 'secret' 2>/dev/null

    And found nothing. Perhaps this is because I have installed varnish from macports.

    1. Anonymous

      The secret should be in /etc/varnish unless macports places the varnish global config folders elsewhere.

  6. Anonymous

    any examples of vcl for ESI?

  7. Anonymous

    can you include (post) apache configuration as well?

  8. Anonymous

    Hello Mark, 

    I use the default.vcl you provided but my problem is I cannot login. Some cookie problem. 

    Ubuntu 12.04 / Apache2 / Varnish3 / Varnish module 7.x beta

  9. Could you give more information? Exactly what happens? What are the headers sent from the server? How are they different to the headers from Apache? ... etc

  10. Anonymous

    These are the response headers when I click "login" : . I can actually login if I point my port to :8080 (directly apache, not varnish) . My varnish defaults are (only the following, nothing else) :

    DAEMON_OPTS="-a :80 \
    -T localhost:6082 \
    -f /etc/varnish/default.vcl \
    -S /etc/varnish/secret \
    -s file,/var/lib/varnish/$INSTANCE/varnish_storage.bin,128M"

    1. Anonymous

      These are the response headers from a succesful login on :8080 .. there's quite some difference....

      1. Anonymous

        Actually the Varnish module says it cannot connect to Varnish  (localhost:6082) and one observation; If I login via :8080 , and then go back to :80, the cookie remains and I am able to surf /admin on :80... As soon as I delete all browser cookies of course, I'm locked-out .. 

  11. Anonymous

    Thanks for this the VCL works for me. It solves my problem regarding not caching logged-in users.

  12. Anonymous

    Thank you mark! This works with me. I blog about this too and link this page:

  13. Anonymous

    In order for me to get this working with the latest git version of Varnish, I had to rename "vcl_fetch" "vcl_backend_response", and I had to change "req.url" to "bereq.url" in the same event handler.

  14. Anonymous

    I am unable to restart varnish after using this vcl. Is there anything i can do to get some error messages? I am using varnish 3

  15. Anonymous

    Unable to restart, was my bad. So this vcl works.


    Now only have to figure out why my cache headers always have miss...

  16. Anonymous

    I can not start varnish when use this

  17. Anonymous

    Thanks for the file.  I have tried example files without succesfully caching content in varnish.  This one did the trick.

  18. Anonymous

    Not Woking for me....

    Please help...

    Unable to start Varnish Service...

    1. Anonymous

      Make sure apache is not running on the same port.

  19. Anonymous

    I'm struggling with this, I can contact mysite on and varnish starts ok.

    When I run varnishlog and access the site the first error is "FetchError   c no backend connection" I have two network address on internal and on external and apache is configured to listen *:8080

    I have tried setting my backend to both internal and external IP, internal IP, localhost, and the site domain name. 

    internal IP

    external IP

    domain (this currently does not resolve to the above IP addres as this is a new server, I have a manual entry in the host file against the external IP)

    backend default {
      .host = "";
      .port = "8080";

    DAEMON_OPTS="-a :80 \

                 -T localhost:6082 \

                 -f /etc/varnish/default.vcl \

                 -S /etc/varnish/secret \

                 -s malloc,128m"


    Apache ports.conf has "listen *:8080" and all virtual hosts are set to the same *:8080

    Any help would be appreciated.

    Cheers  Dan