readme changelog updated, stable tag updated 1.4.3
readme changelog updated, stable tag updated

 Binary files a/assets/banner-772x250.png and b/assets/banner-772x250.png differ
 Binary files a/assets/screenshot-1.png and b/assets/screenshot-1.png differ
 Binary files a/assets/screenshot-2.png and b/assets/screenshot-2.png differ
 Binary files a/assets/screenshot-3.png and b/assets/screenshot-3.png differ
 Binary files a/assets/screenshot-4.png and b/assets/screenshot-4.png differ
 Binary files /dev/null and b/assets/screenshot-5.png differ
 Binary files /dev/null and b/assets/screenshot-6.png differ
file:a/icon.png -> file:b/icon.png
 Binary files a/icon.png and b/icon.png differ
 Binary files /dev/null and b/languages/vcaching-ro_RO.mo differ
--- /dev/null
+++ b/languages/vcaching-ro_RO.po
@@ -1,1 +1,171 @@
+# Translation of Development (trunk) in Romanian
+# This file is distributed under the same license as the Development (trunk) package.
+msgid ""
+msgstr ""
+"PO-Revision-Date: 2015-11-26 15:42:47+0000\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"Plural-Forms: nplurals=3; plural=(n==1 ? 0 : (n==0 || (n%100 > 0 && n%100 < 20)) ? 1 : 2);\n"
+"X-Generator: GlotPress/1.0-alpha-1100\n"
+"Project-Id-Version: Development (trunk)\n"
 
+#: vcaching.php:505
+msgid "Settings"
+msgstr "Setari"
+
+#: vcaching.php:495
+msgid "Purge"
+msgstr "Sterge"
+
+#: vcaching.php:616
+msgid "URL"
+msgstr "URL-ul"
+
+#: vcaching.php:623
+msgid "Relative URL to purge. Example : /wp-content/uploads/.*"
+msgstr "URL relativ pentru stergere. Exemplu : /wp-content/uploads/.*"
+
+#: vcaching.php:351
+msgid "Trying to purge URL :"
+msgstr "Incercare de stergere URL :"
+
+#: vcaching.php:478
+msgid "Console"
+msgstr "Consolă"
+
+#: vcaching.php:476
+msgid "Options"
+msgstr "Opţiuni"
+
+#: vcaching.php:508
+msgid "Homepage cache TTL"
+msgstr "Cache TTL homepage "
+
+#: vcaching.php:509
+msgid "Cache TTL"
+msgstr "Cache TTL"
+
+#: vcaching.php:510
+msgid "IPs"
+msgstr "IPs"
+
+#: vcaching.php:511
+msgid "Dynamic host"
+msgstr "Host dinamic"
+
+#: vcaching.php:513
+msgid "Hosts"
+msgstr "Domenii"
+
+#: vcaching.php:515
+msgid "Override default TTL"
+msgstr "Suprascrie TTL"
+
+#: vcaching.php:516
+msgid "Purge key"
+msgstr "Cheia pentru purge"
+
+#: vcaching.php:517
+msgid "Enable debug"
+msgstr "Activeaza debug"
+
+#: vcaching.php:536
+msgid "Enable Varnish Caching"
+msgstr "Activeaza caching Varnish"
+
+#: vcaching.php:544
+msgid "Time to live in seconds in Varnish cache for homepage"
+msgstr "Secunde de caching in cache Varnish pentru homepage"
+
+#: vcaching.php:552
+msgid "Time to live in seconds in Varnish cache"
+msgstr "Secunde de caching in cache Varnish"
+
+#: vcaching.php:560
+msgid "Comma separated ip/ip:port. Example : 192.168.0.2,192.168.0.3:8080"
+msgstr "ip/ip:port separate de virgula. Exemple : 192.168.0.2,192.168.0.3:8080"
+
+#: vcaching.php:569
+msgid "Uses the $_SERVER['HTTP_HOST'] as hash for Varnish. This means the purge cache action will work on the domain you're on.<br />Use this option if you use only one domain."
+msgstr "Foloseste $_SERVER['HTTP_HOST'] ca hash pentru Varnish. Asta inseamna ca actiunea de purge va functiona doar pe domeniul care esti.<br />Foloseste aceasta optiune daca folosesti un singur domeniu."
+
+#: vcaching.php:579
+msgid "Comma separated hostnames. Varnish uses the hostname to create the cache hash. For each IP, you must set a hostname.<br />Use this option if you use multiple domains."
+msgstr "Domenii separate de virgula. Varnish foloseste domeniul pentru a creea hash-ul pentru cache. Pentru fiecare IP, trebuie sa setezi un domeniu.<br />Foloseste aceasta optiune daca folosesti mai multe domenii."
+
+#: vcaching.php:588
+msgid "Override default TTL on each post/page."
+msgstr "Suprascrie TTL pentru fiecare post/pagina."
+
+#: vcaching.php:597
+msgid "Key used to purge Varnish cache. It is sent to Varnish as X-VC-Purge-Key header. Use a SHA-256 hash.<br />If you can't use ACL's, use this option."
+msgstr "Cheie folosita la stergerea cacheului. Este trimisa catre Varnish ca headerul X-VC-Purge-Key. Foloseste un hash gen SHA-256.<br />Daca nu poti folosi ACL, foloseste aceasta optiune."
+
+#: vcaching.php:607
+msgid "Send all debugging headers to the client. Also shows complete response from Varnish on purge all."
+msgstr "Trimite toate headerele pentru debug catre client. De asemenea va arata raspunsul complet dat de Varnish la actiunea de sterge tot cacheul."
+
+#. Plugin Name of the plugin/theme
+msgid "VCaching"
+msgstr "VCaching"
+
+#. Plugin URI of the plugin/theme
+msgid "http://wordpress.org/extend/plugins/vcaching/"
+msgstr "http://wordpress.org/extend/plugins/vcaching/"
+
+#. Description of the plugin/theme
+msgid "WordPress Varnish Cache integration."
+msgstr "Integrare WordPress cu Varnish Cache."
+
+#. Author of the plugin/theme
+msgid "Razvan Stanga"
+msgstr "Razvan Stanga"
+
+#. Author URI of the plugin/theme
+msgid "http://git.razvi.ro/"
+msgstr "http://git.razvi.ro/"
+
+#: vcaching.php:46
+msgid "Not required. If filled in overrides default TTL of %s seconds. 0 means no caching."
+msgstr "Nu este obligatoriu. Daca este completat, va suprascrie TTL-ul de baza de %s secunde. 0 inseamna cache dezactivat."
+
+#: vcaching.php:242
+msgid "Varnish message:"
+msgstr "Mesaj de la Varnish:"
+
+#: vcaching.php:247
+msgid "Please set the IPs for Varnish!"
+msgstr "Te rog sa setezi IP-urile pentru Varnish."
+
+#: vcaching.php:252
+msgid "Varnish Caching requires you to use custom permalinks. Please go to the <a href=\"options-permalink.php\">Permalinks Options Page</a> to configure them."
+msgstr "Varnish Caching are nevoie sa folosesti custom permalinks. Te rugam mergi la <a href=\"options-permalink.php\">Permalinks Options Page</a> pentru a le configura."
+
+#: vcaching.php:259 vcaching.php:262 vcaching.php:278
+msgid "Purge ALL Varnish Cache"
+msgstr "Sterge TOT cacheul Varnish"
+
+#: vcaching.php:273
+msgid "Please setup Varnish IPs to be able to use <a href=\"%1$s\">Varnish Caching</a>."
+msgstr "Te rugam sa setezi IP-urile pentru a putea folosi <a href=\"%1$s\">Varnish Caching</a>."
+
+#: vcaching.php:275
+msgid "<a href=\"%1$s\">Varnish Caching</a> automatically purges your posts when published or updated. Sometimes you need a manual flush."
+msgstr "<a href=\"%1$s\">Varnish Caching</a> sterge automat cache-ul cand publici sau modifici un post. Uneori e nevoie si de o stergere manuala."
+
+#: vcaching.php:276
+msgid "Press the button below to force it to purge your entire cache."
+msgstr "Apasa butonul de mai jos pentru a forta stergerea totala a cache-ului."
+
+#: vcaching.php:280
+msgid "You do not have permission to purge the cache for the whole site. Please contact your adminstrator."
+msgstr "Nu ai permisiunea sa stergi tot cache-ul. Te rugam contacteaza un administrator."
+
+#: vcaching.php:465 vcaching.php:473
+msgid "Varnish Caching"
+msgstr "Caching Varnish"
+
+#: vcaching.php:507
+msgid "Enable"
+msgstr "Activare"

 Binary files /dev/null and b/languages/vcaching.mo differ
--- /dev/null
+++ b/languages/vcaching.po
@@ -1,1 +1,159 @@
+# Translation of Development (trunk) in English (Canada)
+# This file is distributed under the same license as the Development (trunk) package.
+msgid ""
+msgstr ""
+"PO-Revision-Date: 2015-11-26 07:44:46+0000\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+"Plural-Forms: nplurals=2; plural=n != 1;\n"
+"X-Generator: GlotPress/1.0-alpha-1100\n"
+"Project-Id-Version: Development (trunk)\n"
 
+#: vcaching.php:481
+msgid "Console"
+msgstr "Console"
+
+#: vcaching.php:619
+msgid "Purge URL"
+msgstr ""
+
+#: vcaching.php:626
+msgid "URL to purge"
+msgstr ""
+
+#: vcaching.php:479
+msgid "Options"
+msgstr "Options"
+
+#: vcaching.php:511
+msgid "Homepage cache TTL"
+msgstr "Homepage cache TTL"
+
+#: vcaching.php:512
+msgid "Cache TTL"
+msgstr "Cache TTL"
+
+#: vcaching.php:513
+msgid "IPs"
+msgstr "IPs"
+
+#: vcaching.php:514
+msgid "Dynamic host"
+msgstr "Dynamic host"
+
+#: vcaching.php:516
+msgid "Hosts"
+msgstr "Hosts"
+
+#: vcaching.php:518
+msgid "Override default TTL"
+msgstr "Override default TTL"
+
+#: vcaching.php:519
+msgid "Purge key"
+msgstr "Purge key"
+
+#: vcaching.php:520
+msgid "Enable debug"
+msgstr "Enable debug"
+
+#: vcaching.php:539
+msgid "Enable Varnish caching"
+msgstr "Enable Varnish caching"
+
+#: vcaching.php:547
+msgid "Time to live in seconds in Varnish cache for homepage"
+msgstr "Time to live in seconds in Varnish cache for homepage"
+
+#: vcaching.php:555
+msgid "Time to live in seconds in Varnish cache"
+msgstr "Time to live in seconds in Varnish cache"
+
+#: vcaching.php:563
+msgid "Comma separated ip/ip:port. Example : 192.168.0.2,192.168.0.3:8080"
+msgstr "Comma separated ip/ip:port. Example : 192.168.0.2,192.168.0.3:8080"
+
+#: vcaching.php:572
+msgid "Uses the $_SERVER['HTTP_HOST'] as hash for Varnish. This means the purge cache action will work on the domain you're on.<br />Use this option if you use only one domain."
+msgstr "Uses the $_SERVER['HTTP_HOST'] as hash for Varnish. This means the purge cache action will work on the domain you're on.<br />Use this option if you use only one domain."
+
+#: vcaching.php:582
+msgid "Comma separated hostnames. Varnish uses the hostname to create the cache hash. For each IP, you must set a hostname.<br />Use this option if you use multiple domains."
+msgstr "Comma separated hostnames. Varnish uses the hostname to create the cache hash. For each IP, you must set a hostname.<br />Use this option if you use multiple domains."
+
+#: vcaching.php:591
+msgid "Override default TTL on each post/page."
+msgstr "Override default TTL on each post/page."
+
+#: vcaching.php:600
+msgid "Key used to purge Varnish cache. It is sent to Varnish as X-VC-Purge-Key header. Use a SHA-256 hash.<br />If you can't use ACL's, use this option."
+msgstr "Key used to purge Varnish cache. It is sent to Varnish as X-VC-Purge-Key header. Use a SHA-256 hash.<br />If you can't use ACL's, use this option."
+
+#: vcaching.php:610
+msgid "Send all debugging headers to the client. Also shows complete response from Varnish on purge all."
+msgstr "Send all debugging headers to the client. Also shows complete response from Varnish on purge all."
+
+#. Plugin Name of the plugin/theme
+msgid "VCaching"
+msgstr "VCaching"
+
+#. Plugin URI of the plugin/theme
+msgid "http://wordpress.org/extend/plugins/vcaching/"
+msgstr "http://wordpress.org/extend/plugins/vcaching/"
+
+#. Description of the plugin/theme
+msgid "WordPress Varnish Cache integration."
+msgstr "WordPress Varnish Cache integration."
+
+#. Author of the plugin/theme
+msgid "Razvan Stanga"
+msgstr "Razvan Stanga"
+
+#. Author URI of the plugin/theme
+msgid "http://git.razvi.ro/"
+msgstr "http://git.razvi.ro/"
+
+#: vcaching.php:46
+msgid "Not required. If filled in overrides default TTL of %s seconds. 0 means no caching."
+msgstr "Not required. If filled in overrides default TTL of %s seconds. 0 means no caching."
+
+#: vcaching.php:242
+msgid "Varnish message:"
+msgstr "Varnish message:"
+
+#: vcaching.php:247
+msgid "Please set the IPs for Varnish!"
+msgstr "Please set the IPs for Varnish!"
+
+#: vcaching.php:252
+msgid "Varnish Caching requires you to use custom permalinks. Please go to the <a href=\"options-permalink.php\">Permalinks Options Page</a> to configure them."
+msgstr "Varnish Caching requires you to use custom permalinks. Please go to the <a href=\"options-permalink.php\">Permalinks Options Page</a> to configure them."
+
+#: vcaching.php:259 vcaching.php:262 vcaching.php:278
+msgid "Purge ALL Varnish Cache"
+msgstr "Purge ALL Varnish Cache"
+
+#: vcaching.php:273
+msgid "Please setup Varnish IPs to be able to use <a href=\"%1$s\">Varnish Caching</a>."
+msgstr "Please setup Varnish IPs to be able to use <a href=\"%1$s\">Varnish Caching</a>."
+
+#: vcaching.php:275
+msgid "<a href=\"%1$s\">Varnish Caching</a> automatically purges your posts when published or updated. Sometimes you need a manual flush."
+msgstr "<a href=\"%1$s\">Varnish Caching</a> automatically purges your posts when published or updated. Sometimes you need a manual flush."
+
+#: vcaching.php:276
+msgid "Press the button below to force it to purge your entire cache."
+msgstr "Press the button below to force it to purge your entire cache."
+
+#: vcaching.php:280
+msgid "You do not have permission to purge the cache for the whole site. Please contact your adminstrator."
+msgstr "You do not have permission to purge the cache for the whole site. Please contact your adminstrator."
+
+#: vcaching.php:467 vcaching.php:469 vcaching.php:476
+msgid "Varnish Caching"
+msgstr "Varnish Caching"
+
+#: vcaching.php:510
+msgid "Enable"
+msgstr "Enable"

file:a/readme.txt -> file:b/readme.txt
--- a/readme.txt
+++ b/readme.txt
@@ -1,18 +1,32 @@
-=== VCaching ===
-Donate: PAYPAL razvan_stanga@yahoo.com
+=== Varnish Caching ===
+Donate link: www.paypal.com/use/email/razvan_stanga@yahoo.com
 Contributors: razvanstanga
-Tags: varnish, purge, cache
+Tags: varnish, purge, cache, caching, optimization, performance, traffic
 Requires at least: 4.0
-Tested up to: 4.3
-Stable tag: 1.2.2
+Tested up to: 4.5
+Stable tag: 1.4.3
 License: GPLv2 or later
 
-Varnish Cache Wordpress integration
+Wordpress Varnish Cache 3.x/4.x integration
 
 == Description ==
-Varnish Cache Wordpress integration
+Complete Wordpress Varnish Cache 3.x/4.x integration.
 
-You can control from the Varnish Cache admin panel the following :
+This plugin handles all integration with Varnish Cache. It was designed for high traffic websites.
+
+Main features
+
+* admin interface, see screenshots
+* console for manual purges, supports regular expressions so you can purge an entire folder or just a single file
+* supports every type of Varnish Cache implementation, see screenshots for examples
+* unlimited number of Varnish Cache servers
+* use of custom headers when communicating with Varnish Cache does not interfere with other caching plugins, cloudflare, etc
+* Varnish Cache configuration generator
+* purge key method so you don't need to setup ACLs
+* debugging
+* actively maintained
+
+You can control the following from the Varnish Caching admin panel :
 
 * Enable/Disable caching
 * Homepage cache TTL
@@ -20,20 +34,20 @@
 * IPs/Hosts to clear cache to support every type of Varnish Cache implementation
 * Override default TTL in posts/pages
 * Purge key based PURGE
+* Logged in cookie
 * Debugging option
-* console precise manual purges
+* console for precise manual purges
 
-This plugin also purges Varnish Cache when your site is modified.
+This plugin also auto purges Varnish Cache when your site is modified.
 
 Varnish Caching sends a PURGE request to Varnish Cache when a page or post is modified. This occurs when editing, publishing, commenting or deleting an item, and when changing themes.
-
-<a href="https://www.varnish-cache.org/">Varnish</a> is a web application accelerator also known as a caching HTTP reverse proxy. You install it in front of any server that speaks HTTP and configure it to cache the contents. This plugin <em>does not</em> install Varnish for you, nor does it configure Varnish for WordPress. It's expected you already did that on your own using the provided config files.
-
 Not all pages are purged every time, depending on your Varnish configuration. When a post, page, or custom post type is edited, or a new comment is added, <em>only</em> the following pages will purge:
 
 * The front page
 * The post/page edited
 * Any categories or tags associated with the page
+
+<a href="https://www.varnish-cache.org/">Varnish Cache</a> is a web application accelerator also known as a caching HTTP reverse proxy. You install it in front of any server that speaks HTTP and configure it to cache the contents. This plugin <em>does not</em> install Varnish for you, nor does it configure Varnish for WordPress. It's expected you already did that on your own using the provided config files.
 
 Inspired from the following :
 
@@ -46,14 +60,19 @@
 
 == Installation ==
 
-Use the provided config files for Varnish Cache. Just edit the backend IP/port and ACLs.
-You can also use the purge key method. You must fill in lib/purge.vcl the purge key.
+* You must install Varnish Cache on your server(s)
+* Go to the configuration generator. Fill in the backends/ACLs then download the configuration files
+* Use these configuration files to configure Varnish Cache server(s). Usualy the configuration files are in /etc/varnish. In most cases you must put the downloaded configuration files in /etc/varnish and restart Varnish Cache
+
+Or use the provided Varnish Cache configuration files located in /wp-content/plugins/vcaching/varnish-conf folder.
+
+You can also use the purge key method if you can't setup ACLs. You must fill in lib/purge.vcl the purge key.
 
 == Frequently Asked Questions ==
 
 = What version of Varnish is supported? =
 
-This was built and tested on Varnish 3.x. Soon Varnish 4.x.
+This was built and tested on Varnish 3.x/4.x.
 
 = Why doesn't every page flush when I make a new post? =
 
@@ -61,13 +80,69 @@
 
 = How do I manually purge the whole cache? =
 
-Click the 'Purge ALL Varnish Cache' button on the "Right Now" Dashboard
+Click the 'Purge ALL Varnish Cache' button on the "Right Now" Dashboard.
 
 = How do I manually purge cache? =
 
 Use the console. For example you can purge the whole uploads folder with the URL /wp-content/uploads/.*
 
+= Does this work with W3 Total Cache? =
+
+Yes it does. This plugin uses its own custom headers to communicate with Varnish and does not interfere with the heders sent by W3 Total Cache or any other caching plugin.
+
+= Varnish Statistics =
+
+Statistics need a special setup. More info on the Statistics tab on your Wordpress environment.
+
+= How do I configure my Varnish Cache VCL? =
+
+Use the Varnish Cache configuration generator. Fill in the backends/ACLs then download your configuration files.
+Or use the provided Varnish Cache configuration files located in /wp-content/plugins/vcaching/varnish-conf folder.
+
+= Can I use this with a proxy service like CloudFlare? =
+
+Yes.
+
+= What is logged in cookie? =
+
+Logged in cookie is a special cookie this plugin sets upon user login. Varnish Cache uses this cookie to bypass caching for logged in users.
+
+This is a small step towards securing your site for denial of service attacks. Denial of service attacks can happen if the attacker bypasses Varnish Cache and hits the backend directly.
+With the current configuration and the way Wordpress works, this can still happen with POST/AJAX requests.
+
 == Changelog ==
+
+= 1.4.3 =
+* Truncate option added for too many 'trying to purge' messages. Added check for ZipArchive class to download VCLs.
+
+= 1.4.2 =
+* Bugfix release. Replaced home_url with plugins_url to show VCaching image
+
+= 1.4.1 =
+* Do not cache static files on admin domain
+
+= 1.4 =
+* Varnish Cache configuration generator
+* added `logged in cookie`. This replaces the logged in admin/user based on Wordpress standard cookies to bypass caching
+* moved backends to conf/backend.vcl
+* moved ACLs to conf/acl.vcl
+* updated VCLs. If you are using 1.3 VCLs should upgrade to 1.4
+
+= 1.3.3 =
+* support for Varnish 4
+
+= 1.3.2 =
+* bugfix displaying a single server stats
+
+= 1.3.1 =
+* better varnish statistics, generated by varnishstat
+
+= 1.3 =
+* varnish statistics
+
+= 1.2.3 =
+* wordpress 4.4 compatibility
+* Romanian language file
 
 = 1.2.1 =
 * wp cli
@@ -83,12 +158,15 @@
 
 == Upgrade Notice ==
 
-* none
+= 1.4 =
+Users using 1.3 Varnish Cache VCLs should upgrade to 1.4
 
 == Screenshots ==
 
-1. admin panel
-2. example integration
-3. override default TTL in posts/pages
-4. console purge
+1. Settings admin panel
+2. Console/manual purge admin panel
+3. Varnish Cache Statistics admin panel
+4. Varnish Cache configuration generator admin panel
+5. override default TTL in posts/pages
+6. integration example
 

file:a/varnish-conf/LICENSE (deleted)
--- a/varnish-conf/LICENSE
+++ /dev/null
@@ -1,340 +1,1 @@
-                    GNU GENERAL PUBLIC LICENSE
-                       Version 2, June 1991
 
- Copyright (C) 1989, 1991 Free Software Foundation, Inc.,
- 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301 USA
- Everyone is permitted to copy and distribute verbatim copies
- of this license document, but changing it is not allowed.
-
-                            Preamble
-
-  The licenses for most software are designed to take away your
-freedom to share and change it.  By contrast, the GNU General Public
-License is intended to guarantee your freedom to share and change free
-software--to make sure the software is free for all its users.  This
-General Public License applies to most of the Free Software
-Foundation's software and to any other program whose authors commit to
-using it.  (Some other Free Software Foundation software is covered by
-the GNU Lesser General Public License instead.)  You can apply it to
-your programs, too.
-
-  When we speak of free software, we are referring to freedom, not
-price.  Our General Public Licenses are designed to make sure that you
-have the freedom to distribute copies of free software (and charge for
-this service if you wish), that you receive source code or can get it
-if you want it, that you can change the software or use pieces of it
-in new free programs; and that you know you can do these things.
-
-  To protect your rights, we need to make restrictions that forbid
-anyone to deny you these rights or to ask you to surrender the rights.
-These restrictions translate to certain responsibilities for you if you
-distribute copies of the software, or if you modify it.
-
-  For example, if you distribute copies of such a program, whether
-gratis or for a fee, you must give the recipients all the rights that
-you have.  You must make sure that they, too, receive or can get the
-source code.  And you must show them these terms so they know their
-rights.
-
-  We protect your rights with two steps: (1) copyright the software, and
-(2) offer you this license which gives you legal permission to copy,
-distribute and/or modify the software.
-
-  Also, for each author's protection and ours, we want to make certain
-that everyone understands that there is no warranty for this free
-software.  If the software is modified by someone else and passed on, we
-want its recipients to know that what they have is not the original, so
-that any problems introduced by others will not reflect on the original
-authors' reputations.
-
-  Finally, any free program is threatened constantly by software
-patents.  We wish to avoid the danger that redistributors of a free
-program will individually obtain patent licenses, in effect making the
-program proprietary.  To prevent this, we have made it clear that any
-patent must be licensed for everyone's free use or not licensed at all.
-
-  The precise terms and conditions for copying, distribution and
-modification follow.
-
-                    GNU GENERAL PUBLIC LICENSE
-   TERMS AND CONDITIONS FOR COPYING, DISTRIBUTION AND MODIFICATION
-
-  0. This License applies to any program or other work which contains
-a notice placed by the copyright holder saying it may be distributed
-under the terms of this General Public License.  The "Program", below,
-refers to any such program or work, and a "work based on the Program"
-means either the Program or any derivative work under copyright law:
-that is to say, a work containing the Program or a portion of it,
-either verbatim or with modifications and/or translated into another
-language.  (Hereinafter, translation is included without limitation in
-the term "modification".)  Each licensee is addressed as "you".
-
-Activities other than copying, distribution and modification are not
-covered by this License; they are outside its scope.  The act of
-running the Program is not restricted, and the output from the Program
-is covered only if its contents constitute a work based on the
-Program (independent of having been made by running the Program).
-Whether that is true depends on what the Program does.
-
-  1. You may copy and distribute verbatim copies of the Program's
-source code as you receive it, in any medium, provided that you
-conspicuously and appropriately publish on each copy an appropriate
-copyright notice and disclaimer of warranty; keep intact all the
-notices that refer to this License and to the absence of any warranty;
-and give any other recipients of the Program a copy of this License
-along with the Program.
-
-You may charge a fee for the physical act of transferring a copy, and
-you may at your option offer warranty protection in exchange for a fee.
-
-  2. You may modify your copy or copies of the Program or any portion
-of it, thus forming a work based on the Program, and copy and
-distribute such modifications or work under the terms of Section 1
-above, provided that you also meet all of these conditions:
-
-    a) You must cause the modified files to carry prominent notices
-    stating that you changed the files and the date of any change.
-
-    b) You must cause any work that you distribute or publish, that in
-    whole or in part contains or is derived from the Program or any
-    part thereof, to be licensed as a whole at no charge to all third
-    parties under the terms of this License.
-
-    c) If the modified program normally reads commands interactively
-    when run, you must cause it, when started running for such
-    interactive use in the most ordinary way, to print or display an
-    announcement including an appropriate copyright notice and a
-    notice that there is no warranty (or else, saying that you provide
-    a warranty) and that users may redistribute the program under
-    these conditions, and telling the user how to view a copy of this
-    License.  (Exception: if the Program itself is interactive but
-    does not normally print such an announcement, your work based on
-    the Program is not required to print an announcement.)
-
-These requirements apply to the modified work as a whole.  If
-identifiable sections of that work are not derived from the Program,
-and can be reasonably considered independent and separate works in
-themselves, then this License, and its terms, do not apply to those
-sections when you distribute them as separate works.  But when you
-distribute the same sections as part of a whole which is a work based
-on the Program, the distribution of the whole must be on the terms of
-this License, whose permissions for other licensees extend to the
-entire whole, and thus to each and every part regardless of who wrote it.
-
-Thus, it is not the intent of this section to claim rights or contest
-your rights to work written entirely by you; rather, the intent is to
-exercise the right to control the distribution of derivative or
-collective works based on the Program.
-
-In addition, mere aggregation of another work not based on the Program
-with the Program (or with a work based on the Program) on a volume of
-a storage or distribution medium does not bring the other work under
-the scope of this License.
-
-  3. You may copy and distribute the Program (or a work based on it,
-under Section 2) in object code or executable form under the terms of
-Sections 1 and 2 above provided that you also do one of the following:
-
-    a) Accompany it with the complete corresponding machine-readable
-    source code, which must be distributed under the terms of Sections
-    1 and 2 above on a medium customarily used for software interchange; or,
-
-    b) Accompany it with a written offer, valid for at least three
-    years, to give any third party, for a charge no more than your
-    cost of physically performing source distribution, a complete
-    machine-readable copy of the corresponding source code, to be
-    distributed under the terms of Sections 1 and 2 above on a medium
-    customarily used for software interchange; or,
-
-    c) Accompany it with the information you received as to the offer
-    to distribute corresponding source code.  (This alternative is
-    allowed only for noncommercial distribution and only if you
-    received the program in object code or executable form with such
-    an offer, in accord with Subsection b above.)
-
-The source code for a work means the preferred form of the work for
-making modifications to it.  For an executable work, complete source
-code means all the source code for all modules it contains, plus any
-associated interface definition files, plus the scripts used to
-control compilation and installation of the executable.  However, as a
-special exception, the source code distributed need not include
-anything that is normally distributed (in either source or binary
-form) with the major components (compiler, kernel, and so on) of the
-operating system on which the executable runs, unless that component
-itself accompanies the executable.
-
-If distribution of executable or object code is made by offering
-access to copy from a designated place, then offering equivalent
-access to copy the source code from the same place counts as
-distribution of the source code, even though third parties are not
-compelled to copy the source along with the object code.
-
-  4. You may not copy, modify, sublicense, or distribute the Program
-except as expressly provided under this License.  Any attempt
-otherwise to copy, modify, sublicense or distribute the Program is
-void, and will automatically terminate your rights under this License.
-However, parties who have received copies, or rights, from you under
-this License will not have their licenses terminated so long as such
-parties remain in full compliance.
-
-  5. You are not required to accept this License, since you have not
-signed it.  However, nothing else grants you permission to modify or
-distribute the Program or its derivative works.  These actions are
-prohibited by law if you do not accept this License.  Therefore, by
-modifying or distributing the Program (or any work based on the
-Program), you indicate your acceptance of this License to do so, and
-all its terms and conditions for copying, distributing or modifying
-the Program or works based on it.
-
-  6. Each time you redistribute the Program (or any work based on the
-Program), the recipient automatically receives a license from the
-original licensor to copy, distribute or modify the Program subject to
-these terms and conditions.  You may not impose any further
-restrictions on the recipients' exercise of the rights granted herein.
-You are not responsible for enforcing compliance by third parties to
-this License.
-
-  7. If, as a consequence of a court judgment or allegation of patent
-infringement or for any other reason (not limited to patent issues),
-conditions are imposed on you (whether by court order, agreement or
-otherwise) that contradict the conditions of this License, they do not
-excuse you from the conditions of this License.  If you cannot
-distribute so as to satisfy simultaneously your obligations under this
-License and any other pertinent obligations, then as a consequence you
-may not distribute the Program at all.  For example, if a patent
-license would not permit royalty-free redistribution of the Program by
-all those who receive copies directly or indirectly through you, then
-the only way you could satisfy both it and this License would be to
-refrain entirely from distribution of the Program.
-
-If any portion of this section is held invalid or unenforceable under
-any particular circumstance, the balance of the section is intended to
-apply and the section as a whole is intended to apply in other
-circumstances.
-
-It is not the purpose of this section to induce you to infringe any
-patents or other property right claims or to contest validity of any
-such claims; this section has the sole purpose of protecting the
-integrity of the free software distribution system, which is
-implemented by public license practices.  Many people have made
-generous contributions to the wide range of software distributed
-through that system in reliance on consistent application of that
-system; it is up to the author/donor to decide if he or she is willing
-to distribute software through any other system and a licensee cannot
-impose that choice.
-
-This section is intended to make thoroughly clear what is believed to
-be a consequence of the rest of this License.
-
-  8. If the distribution and/or use of the Program is restricted in
-certain countries either by patents or by copyrighted interfaces, the
-original copyright holder who places the Program under this License
-may add an explicit geographical distribution limitation excluding
-those countries, so that distribution is permitted only in or among
-countries not thus excluded.  In such case, this License incorporates
-the limitation as if written in the body of this License.
-
-  9. The Free Software Foundation may publish revised and/or new versions
-of the General Public License from time to time.  Such new versions will
-be similar in spirit to the present version, but may differ in detail to
-address new problems or concerns.
-
-Each version is given a distinguishing version number.  If the Program
-specifies a version number of this License which applies to it and "any
-later version", you have the option of following the terms and conditions
-either of that version or of any later version published by the Free
-Software Foundation.  If the Program does not specify a version number of
-this License, you may choose any version ever published by the Free Software
-Foundation.
-
-  10. If you wish to incorporate parts of the Program into other free
-programs whose distribution conditions are different, write to the author
-to ask for permission.  For software which is copyrighted by the Free
-Software Foundation, write to the Free Software Foundation; we sometimes
-make exceptions for this.  Our decision will be guided by the two goals
-of preserving the free status of all derivatives of our free software and
-of promoting the sharing and reuse of software generally.
-
-                            NO WARRANTY
-
-  11. BECAUSE THE PROGRAM IS LICENSED FREE OF CHARGE, THERE IS NO WARRANTY
-FOR THE PROGRAM, TO THE EXTENT PERMITTED BY APPLICABLE LAW.  EXCEPT WHEN
-OTHERWISE STATED IN WRITING THE COPYRIGHT HOLDERS AND/OR OTHER PARTIES
-PROVIDE THE PROGRAM "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED
-OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF
-MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE.  THE ENTIRE RISK AS
-TO THE QUALITY AND PERFORMANCE OF THE PROGRAM IS WITH YOU.  SHOULD THE
-PROGRAM PROVE DEFECTIVE, YOU ASSUME THE COST OF ALL NECESSARY SERVICING,
-REPAIR OR CORRECTION.
-
-  12. IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING
-WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MAY MODIFY AND/OR
-REDISTRIBUTE THE PROGRAM AS PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES,
-INCLUDING ANY GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING
-OUT OF THE USE OR INABILITY TO USE THE PROGRAM (INCLUDING BUT NOT LIMITED
-TO LOSS OF DATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY
-YOU OR THIRD PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER
-PROGRAMS), EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE
-POSSIBILITY OF SUCH DAMAGES.
-
-                     END OF TERMS AND CONDITIONS
-
-            How to Apply These Terms to Your New Programs
-
-  If you develop a new program, and you want it to be of the greatest
-possible use to the public, the best way to achieve this is to make it
-free software which everyone can redistribute and change under these terms.
-
-  To do so, attach the following notices to the program.  It is safest
-to attach them to the start of each source file to most effectively
-convey the exclusion of warranty; and each file should have at least
-the "copyright" line and a pointer to where the full notice is found.
-
-    <one line to give the program's name and a brief idea of what it does.>
-    Copyright (C) <year>  <name of author>
-
-    This program is free software; you can redistribute it and/or modify
-    it under the terms of the GNU General Public License as published by
-    the Free Software Foundation; either version 2 of the License, or
-    (at your option) any later version.
-
-    This program is distributed in the hope that it will be useful,
-    but WITHOUT ANY WARRANTY; without even the implied warranty of
-    MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
-    GNU General Public License for more details.
-
-    You should have received a copy of the GNU General Public License along
-    with this program; if not, write to the Free Software Foundation, Inc.,
-    51 Franklin Street, Fifth Floor, Boston, MA 02110-1301 USA.
-
-Also add information on how to contact you by electronic and paper mail.
-
-If the program is interactive, make it output a short notice like this
-when it starts in an interactive mode:
-
-    Gnomovision version 69, Copyright (C) year name of author
-    Gnomovision comes with ABSOLUTELY NO WARRANTY; for details type `show w'.
-    This is free software, and you are welcome to redistribute it
-    under certain conditions; type `show c' for details.
-
-The hypothetical commands `show w' and `show c' should show the appropriate
-parts of the General Public License.  Of course, the commands you use may
-be called something other than `show w' and `show c'; they could even be
-mouse-clicks or menu items--whatever suits your program.
-
-You should also get your employer (if you work as a programmer) or your
-school, if any, to sign a "copyright disclaimer" for the program, if
-necessary.  Here is a sample; alter the names:
-
-  Yoyodyne, Inc., hereby disclaims all copyright interest in the program
-  `Gnomovision' (which makes passes at compilers) written by James Hacker.
-
-  <signature of Ty Coon>, 1 April 1989
-  Ty Coon, President of Vice
-
-This General Public License does not permit incorporating your program into
-proprietary programs.  If your program is a subroutine library, you may
-consider it more useful to permit linking proprietary applications with the
-library.  If this is what you want to do, use the GNU Lesser General
-Public License instead of this License.
-

file:a/varnish-conf/README.rst (deleted)
--- a/varnish-conf/README.rst
+++ /dev/null
@@ -1,149 +1,1 @@
-======================
-varnish-vcl-collection
-======================
 
-Collection of Varnish VCL files.  The purpose of this collection is to make
-it easier to configure varnish for some common setups and behaviors.  Some
-of these files require you to define specific ACLs in your main VCL, and also
-note that the order of including files could change the behavior of Varnish.
-
-The main goal for this VCL Collection is to provide a simple config with just
-a few options that can make Varnish work for the majority of sites. Most of
-the "configuration" is done by choosing which files to include and defining
-ACLs. We hope to provide a robust configuration that can be used with
-relatively little information or control over what is actually running on
-the backend.  This is particularly useful for managed web hosts who want
-to have customers benefit from the performance of a caching proxy without
-limiting what can run on the web backend and without customizing the
-configuration for each customer.
-
-See `wordpress-example.vcl` for an example of how to use this collection
-of VCLs to configure Varnish for a WordPress site.
-
-
-CloudFlare
-==========
-
-If you use CloudFlare and the backend is running `mod_cloudflare` (for Apache)
-or `http_realip_module` (for Nginx), then you should use `lib/cloudflare.vcl`.
-
-CloudFlare uses the HTTP Header `CF-Connecting-IP` to store the original
-client IP address.  Note that unlike the `X-Forwarded-For` Header, this just
-contains the original IP address, not the entire forward chain.
-
-If you are using a CloudFlare Railgun server, or have any other trusted proxy
-servers between Varnish and CloudFlare, you will need to specify them in the
-`cloudflare` ACL.
-
-Also note that you will need to make sure that Varnish's IP is configured
-as trusted in `mod_cloudflare` or the `http_realip_module` on the backend.
-
-Example usage::
-
-	include "lib/cloudflare.vcl";
-
-	acl cloudflare {
-		# put the IP of your Railgun (or proxy) server here
-		# "1.2.3.4";
-	}
-
-
-Mobile Device Optimizaiton
-==========================
-
-Different applications optimize for mobile devices in different ways.  The
-best way is to use an "adaptive" design so that the same HTML is served to
-both desktop and mobile devices.  If your application is "adaptive", then
-no special Varnish config is necessary; all devices will access the same
-objects in the Varnish cache.
-
-However, if your application does serve different content to different
-devices, then you'll need to handle that in Varnish.  Since applications
-do mobile device detection differently, the VCL code included here is
-intentionally limited and simple.  Crafting a custom configuration to handle
-the way your application treats mobile devices will usually give better
-results than using one of the following standard configs.
-
-`lib/mobile_cache.vcl` simply adds the string `mobile` to the hash data to
-give mobile devices a separate cache from non-mobile devices.  This is only
-viable if your application serves just 2 different versions of each page
-depending on if the visitor is on a mobile device or not (and if the
-application uses the same method to detect mobile devices).  Any disagreement
-between `mobile_cache.vcl` and your backend on what User-Agents should be
-considered "mobile" could mean that the incorrect versions of pages are
-served to some visitors.
-
-`lib/mobile_pass.vcl` simply disables caching for mobile devices.  This is
-not good for performance, but will at least will prevent serving the
-incorrect version of pages to mobile visitors.
-
-
-HTTP Purging
-============
-
-Include `lib/purge.vcl` to allow purging pages from the cache using the HTTP
-PURGE method.  This uses the ban feature of varnish and will make bans take
-advantage of Varnish's ban-lurker.  You will need to specify a `purge` ACL
-so that only requests coming from your application are allowed to purge.
-
-Example usage::
-
-	include "lib/purge.vcl";
-
-	acl purge {
-		# include the IP of your app if it isn't on localhost
-		"localhost";
-		"127.0.0.1";
-	}
-
-There are several different possible behaviors of HTTP purging which can be
-controlled with the X-Purge-Method HTTP header.  This config will be smart
-and attempt to automatically pick the best method based on the URL if you
-don't use an X-Purge-Method header.  See the comments in `lib/purge.vcl` for
-details.
-You can also use the X-VC-Purge-Key method. Generate a MD5/SHA-256 hash and fill it on line
-if (req.http.X-VC-Purge-Key == "hash-to-be-filled-in") {
-in lib/purge.vcl. Then use the same hash in Varnish Caching WP admin.
-
-
-Static File Caching
-===================
-
-Include `lib/static.vcl` to use a simple set of rules to cache static files.
-This will ignore the query string part of request URLs, and discard all
-cookies for these requests.  This will also cache static files for 24 hours.
-
-The cache behavior for this vcl can be bypassed by adding `nocache` to the
-url.  For example, `http://example.com/foo.jpg?nocache` will always
-retrieve the file from the backend instead of serving from the cache.
-
-
-Big Files
-=========
-
-Varnish cannot cache files larger than the entire cache.  Additionally, a few
-large files could potentially fill up the cache and force many more small
-files to be removed from the cache. Use `lib/bigfiles.vcl` or
-`lib/bigfiles_pipe.vcl` to prevent caching files larger than 10 MB.  This
-size was chosen because this should allow most common website assets to be
-cached.  Files larger than 10 MB such as videos, long podcasts, or binary
-downloads are better suited to be served with a CDN or some server separate
-from your main web application.  This config will still allow Varnish to
-serve these large files, but the files will always be retrieved from the
-backend.
-
-`lib/bigfiles.vcl` marks files with `hit_for_pass` when they are above the
-size threshold.  However this only works in Varnish 3.0.3 or later.  Earlier
-versions of Varnish will instead show an internal server error when this
-method is used.  In the case of these older versions of Varnish, you should
-use `lib/bigfiles_pipe.vcl`, which instead pipes the request.
-
-Your main VCL must have `import std;`.  This import line is not included
-within the files themselves because having an import multiple times in a
-Varnish config (counting all included files) produces a compile error.
-
-Example usage::
-
-	import std;
-	include "lib/bigfiles.vcl";
-

--- a/varnish-conf/default.vcl
+++ /dev/null
@@ -1,155 +1,1 @@
-backend default {
-    .host = "192.168.0.2";
-    .port = "80";
-}
 
-import std;
-
-include "lib/xforward.vcl";
-include "lib/cloudflare.vcl";
-include "lib/purge.vcl";
-include "lib/bigfiles.vcl";
-include "lib/static.vcl";
-
-acl cloudflare {
-    # set this ip to your Railgun IP (if applicable)
-    # "1.2.3.4";
-}
-
-acl purge {
-    "localhost";
-    "127.0.0.1";
-    #"192.168.0.2";
-}
-
-# Pick just one of the following:
-# (or don't use either of these if your application is "adaptive")
-# include "lib/mobile_cache.vcl";
-# include "lib/mobile_pass.vcl";
-
-### WordPress-specific config ###
-sub vcl_recv {
-    # pipe on weird http methods
-    if (req.request !~ "^GET|HEAD|PUT|POST|TRACE|OPTIONS|DELETE$") {
-        return(pipe);
-    }
-
-    # redirect yourdomain.com to www.yourdomain.com
-    if (req.http.host ~ "^yourdomain\.com$") {
-        error 750 "http://www.yourdomain.com" + req.url;
-    }
-
-    # if you use a subdomain for wp-admin, do not cache it
-    if (req.http.host ~ "admin.yourdomain.com") {
-        return(pass);
-    }
-
-    ### Check for reasons to bypass the cache!
-    # never cache anything except GET/HEAD
-    if (req.request != "GET" && req.request != "HEAD") {
-        return(pass);
-    }
-
-    # don't cache logged-in users or authors
-    if (req.http.Cookie ~ "wp-postpass_|wordpress_logged_in_|comment_author|PHPSESSID") {
-        set req.http.X-VC-GotSession = "true";
-        return(pass);
-    }
-
-    # don't cache ajax requests
-    if (req.http.X-Requested-With == "XMLHttpRequest") {
-        return(pass);
-    }
-
-    # don't cache these special pages
-    if (req.url ~ "nocache|wp-admin|wp-(comments-post|login|activate|mail)\.php|bb-admin|server-status|control\.php|bb-login\.php|bb-reset-password\.php|register\.php") {
-        return(pass);
-    }
-
-    ### looks like we might actually cache it!
-    # fix up the request
-    set req.grace = 2m;
-    set req.url = regsub(req.url, "\?replytocom=.*$", "");
-
-    # strip query parameters from all urls (so they cache as a single object)
-    # be carefull using this option
-    #if (req.url ~ "\?.*") {
-    #    set req.url = regsub(req.url, "\?.*", "");
-    #}
-
-    # Remove has_js, Google Analytics __*, and wooTracker cookies.
-    set req.http.Cookie = regsuball(req.http.Cookie, "(^|;\s*)(__[a-z]+|has_js|wooTracker)=[^;]*", "");
-    set req.http.Cookie = regsub(req.http.Cookie, "^;\s*", "");
-    if (req.http.Cookie ~ "^\s*$") {
-        unset req.http.Cookie;
-    }
-
-    return(lookup);
-}
-
-sub vcl_hash {
-    # Add the browser cookie only if a WordPress cookie found.
-    if (req.http.Cookie ~ "wp-postpass_|wordpress_logged_in_|comment_author|PHPSESSID") {
-        hash_data(req.http.Cookie);
-    }
-}
-
-sub vcl_fetch {
-    # make sure grace is at least 2 minutes
-    if (beresp.grace < 2m) {
-        set beresp.grace = 2m;
-    }
-
-    # overwrite ttl with X-VC-TTL
-    if (beresp.http.X-VC-TTL) {
-        set beresp.ttl = std.duration(beresp.http.X-VC-TTL + "s", 0s);
-    }
-
-    # catch obvious reasons we can't cache
-    if (beresp.http.Set-Cookie) {
-        set beresp.ttl = 0s;
-    }
-
-    # You don't wish to cache content for logged in users
-    if (req.http.Cookie ~ "wp-postpass_|wordpress_logged_in_|comment_author|PHPSESSID") {
-        set beresp.http.X-VC-Cacheable = "NO:Got Session";
-        return(hit_for_pass);
-
-    # Varnish determined the object was not cacheable
-    } else if (beresp.ttl <= 0s) {
-        set beresp.http.X-VC-Cacheable = "NO:Not Cacheable";
-        return(hit_for_pass);
-
-    # You are respecting the Cache-Control=private header from the backend
-    } else if (beresp.http.Cache-Control ~ "private") {
-        set beresp.http.X-VC-Cacheable = "NO:Cache-Control=private";
-        return(hit_for_pass);
-
-    # You are respecting the X-VC-Enabled=true header from the backend
-    } else if (beresp.http.X-VC-Enabled ~ "true") {
-        set beresp.http.X-VC-Cacheable = "YES";
-
-    # Do not cache object
-    } else if (beresp.http.X-VC-Enabled ~ "false") {
-        set beresp.http.X-VC-Cacheable = "NO:Disabled";
-        set beresp.ttl = 0s;
-    }
-
-    # Avoid caching error responses
-    if (beresp.status == 404 || beresp.status >= 500) {
-        set beresp.ttl   = 0s;
-        set beresp.grace = 15s;
-    }
-
-    # Deliver the content
-    return(deliver);
-}
-
-sub vcl_error {
-    if (obj.status == 750) {
-        set obj.http.Location = obj.response;
-        set obj.status = 302;
-        return(deliver);
-    }
-}
-

--- a/varnish-conf/lib/bigfiles.vcl
+++ /dev/null
@@ -1,9 +1,1 @@
-# bigfiles.vcl -- Bypass Cache for Large Files
 
-sub vcl_fetch {
-    # Bypass cache for files > 10 MB
-    if (std.integer(beresp.http.Content-Length, 0) > 10485760) {
-        return (hit_for_pass);
-    }
-}
-

--- a/varnish-conf/lib/bigfiles_pipe.vcl
+++ /dev/null
@@ -1,23 +1,1 @@
-# bigfiles_pipe.vcl -- Pipe for Large Files
 
-# You must have "import std;" in your main vcl:
-# import std;
-
-# NOTE: Using restart and pipe is a workaround for a bug in varnish prior to
-# 3.0.3.  In 3.0.3+, hit_for_pass in vcl_fetch is all that is necessary.
-
-sub vcl_recv {
-    if (req.http.X-Pipe-Big-File && req.restarts > 0) {
-        unset req.http.X-Pipe-Big-File;
-        return (pipe);
-    }
-}
-
-sub vcl_fetch {
-    # Bypass cache for files > 10 MB
-    if (std.integer(beresp.http.Content-Length, 0) > 10485760) {
-        set req.http.X-Pipe-Big-File = "Yes";
-        return (restart);
-    }
-}
-

--- a/varnish-conf/lib/cloudflare.vcl
+++ /dev/null
@@ -1,41 +1,1 @@
-# cloudflare.vcl -- CloudFlare HTTP Headers
 
-# This should generally be loaded first to make sure that the headers
-# get set appropriately for all requests.
-
-acl official_cloudflare {
-    # https://www.cloudflare.com/ips-v4
-    "204.93.240.0"/24;
-    "204.93.177.0"/24;
-    "199.27.128.0"/21;
-    "173.245.48.0"/20;
-    "103.21.244.0"/22;
-    "103.22.200.0"/22;
-    "103.31.4.0"/22;
-    "141.101.64.0"/18;
-    "108.162.192.0"/18;
-    "190.93.240.0"/20;
-    "188.114.96.0"/20;
-    "197.234.240.0"/22;
-    "198.41.128.0"/17;
-    "162.158.0.0"/15;
-    # https://www.cloudflare.com/ips-v6
-    "2400:cb00::"/32;
-    "2606:4700::"/32;
-    "2803:f800::"/32;
-    "2405:b500::"/32;
-    "2405:8100::"/32;
-}
-
-sub vcl_recv {
-    # Set the CF-Connecting-IP header
-    # If the client.ip is trusted, we leave the header alone if present.
-    if (req.http.CF-Connecting-IP) {
-        if (client.ip !~ official_cloudflare && client.ip !~ cloudflare) {
-            set req.http.CF-Connecting-IP = client.ip;
-        }
-    } else {
-        set req.http.CF-Connecting-IP = client.ip;
-    }
-}
-

--- a/varnish-conf/lib/mobile_cache.vcl
+++ /dev/null
@@ -1,20 +1,1 @@
-# mobile_cache.vcl -- Separate cache for mobile clients
 
-# If the User-Agent looks like a mobile device, then we add the string
-# "mobile" to the hash_data.  This results in mobile devices having
-# a separate cache from non-mobile devices.
-#
-# Note that if the backend does anything more sophisticated than having
-# a "desktop" and a "mobile" version of pages (for example serving one
-# page to iPhones and another to Androids), this will not be desirable.
-# Also if the backend disagrees with this logic as far as what is a
-# "mobile" User-Agent, then we may save the wrong version of pages in
-# the cache.
-
-sub vcl_hash {
-    # General User-Agent list (anything that remotely looks like a mobile device)
-    if (req.http.User-Agent ~ "(?i)ipod|android|blackberry|phone|mobile|kindle|silk|fennec|tablet|webos|palm|windows ce|nokia|philips|samsung|sanyo|sony|panasonic|ericsson|alcatel|series60|series40|opera mini|opera mobi|au-mic|audiovox|avantgo|blazer|danger|docomo|epoc|ericy|i-mode|ipaq|midp-|mot-|netfront|nitro|pocket|portalmmm|rover|sie-|symbian|cldc-|j2me|up\.browser|up\.link|vodafone|wap1\.|wap2\.") {
-        hash_data("mobile");
-    }
-}
-

--- a/varnish-conf/lib/mobile_pass.vcl
+++ /dev/null
@@ -1,22 +1,1 @@
-# mobile_pass.vcl -- Mobile pass-through support for Varnish
 
-# This simply bypasses the cache for anything that looks like a mobile
-# (or tablet) device.
-# Also passes through some requests that are specifically for the WordPress
-# Jetpack mobile plugin.
-
-sub vcl_recv {
-    # Rules specifically for the Jetpack Mobile module
-    if (req.url ~ "\?(.*&)?(ak_action|app-download)=") {
-        return(pass);
-    }
-    if (req.http.Cookie ~ "(^|;\s*)akm_mobile=") {
-        return(pass);
-    }
-
-    # General User-Agent blacklist (anything that remotely looks like a mobile device)
-    if (req.http.User-Agent ~ "(?i)ipod|android|blackberry|phone|mobile|kindle|silk|fennec|tablet|webos|palm|windows ce|nokia|philips|samsung|sanyo|sony|panasonic|ericsson|alcatel|series60|series40|opera mini|opera mobi|au-mic|audiovox|avantgo|blazer|danger|docomo|epoc|ericy|i-mode|ipaq|midp-|mot-|netfront|nitro|pocket|portalmmm|rover|sie-|symbian|cldc-|j2me|up\.browser|up\.link|vodafone|wap1\.|wap2\.") {
-        return(pass);
-    }
-}
-

--- a/varnish-conf/lib/purge.vcl
+++ /dev/null
@@ -1,98 +1,1 @@
-# purge.vcl -- Cache Purge Library for Varnish
 
-# Regex purging
-# Treat the request URL as a regular expression.
-sub purge_regex {
-    ban("obj.http.X-VC-Req-URL ~ " + req.url + " && obj.http.X-VC-Req-Host == " + req.http.host);
-}
-
-# Exact purging
-# Use the exact request URL (including any query params)
-sub purge_exact {
-    ban("obj.http.X-VC-Req-URL == " + req.url + " && obj.http.X-VC-Req-Host == " + req.http.host);
-}
-
-# Page purging (default)
-# Use the exact request URL, but ignore any query params
-sub purge_page {
-    set req.url = regsub(req.url, "\?.*$", "");
-    ban("obj.http.X-VC-Req-URL-Base == " + req.url + " && obj.http.X-VC-Req-Host == " + req.http.host);
-}
-
-# The purge behavior can be controlled with the X-VC-Purge-Method header.
-#
-# Setting the X-VC-Purge-Method header to contain "regex" or "exact" will use
-# those respective behaviors.  Any other value for the X-Purge header will
-# use the default ("page") behavior.
-#
-# The X-VC-Purge-Method header is not case-sensitive.
-#
-# If no X-VC-Purge-Method header is set, the request url is inspected to attempt
-# a best guess as to what purge behavior is expected.  This should work for
-# most cases, although if you want to guarantee some behavior you should
-# always set the X-VC-Purge-Method header.
-
-sub vcl_recv {
-    if (req.request == "PURGE") {
-        if (req.http.X-VC-Purge-Key == "ff93c3cb929cee86901c7eefc8088e9511c005492c6502a930360c02221cf8f4") {
-            set req.http.X-VC-Purge-Key-Auth = "true";
-        } else {
-            set req.http.X-VC-Purge-Key-Auth = "false";
-        }
-        if (client.ip !~ purge && req.http.X-VC-Purge-Key-Auth != "true") {
-            error 405 "Not allowed from " + client.ip;
-        }
-
-        if (req.http.X-VC-Purge-Method) {
-            if (req.http.X-VC-Purge-Method ~ "(?i)regex") {
-                call purge_regex;
-            } elsif (req.http.X-VC-Purge-Method ~ "(?i)exact") {
-                call purge_exact;
-            } else {
-                call purge_page;
-            }
-        } else {
-            # No X-Purge-Method header was specified.
-            # Do our best to figure out which one they want.
-            if (req.url ~ "\.\*" || req.url ~ "^\^" || req.url ~ "\$$" || req.url ~ "\\[.?*+^$|()]") {
-                call purge_regex;
-            } elsif (req.url ~ "\?") {
-                call purge_exact;
-            } else {
-                call purge_page;
-            }
-        }
-        error 200 "Purged " + req.url + " " + req.http.host;
-    }
-}
-
-sub vcl_fetch {
-    set beresp.http.X-VC-Req-Host = req.http.host;
-    set beresp.http.X-VC-Req-URL = req.url;
-    set beresp.http.X-VC-Req-URL-Base = regsub(req.url, "\?.*$", "");
-}
-
-sub vcl_deliver {
-    unset resp.http.X-VC-Req-Host;
-    unset resp.http.X-VC-Req-URL;
-    unset resp.http.X-VC-Req-URL-Base;
-
-    if (obj.hits > 0) {
-        set resp.http.X-VC-Cache = "HIT";
-    } else {
-        set resp.http.X-VC-Cache = "MISS";
-    }
-
-    if (resp.http.X-VC-Debug ~ "true") {
-        set resp.http.X-VC-Hash = req.url+"#"+req.http.host;
-    } else {
-        unset resp.http.X-VC-Enabled;
-        unset resp.http.X-VC-Cache;
-        unset resp.http.X-VC-Debug;
-        unset resp.http.X-VC-Cacheable;
-        unset resp.http.X-VC-Purge-Key-Auth;
-        unset resp.http.X-VC-TTL;
-        unset resp.http.X-VC-GotSession;
-    }
-}
-

--- a/varnish-conf/lib/static.vcl
+++ /dev/null
@@ -1,27 +1,1 @@
-# static.vcl -- Static File Caching for Varnish
 
-sub vcl_recv {
-    if (req.request ~ "^(GET|HEAD)$" && req.url ~ "\.(jpg|jpeg|gif|png|ico|css|zip|tgz|gz|rar|bz2|pdf|txt|tar|wav|bmp|rtf|js|flv|swf|html|htm)(\?.*)?$") {
-        # disable this if you want
-        if (req.url ~ "nocache") {
-            return(pass);
-        }
-        set req.url = regsub(req.url, "\?.*$", "");
-        # unset cookie only if no http auth
-        if (!req.http.Authorization) {
-            unset req.http.Cookie;
-        }
-        set req.grace = 2m;
-        return(lookup);
-    }
-}
-
-sub vcl_fetch {
-    if (req.request ~ "^(GET|HEAD)$" && req.url ~ "\.(jpg|jpeg|gif|png|ico|css|zip|tgz|gz|rar|bz2|pdf|txt|tar|wav|bmp|rtf|js|flv|swf|html|htm)$") {
-        # overwrite ttl with X-VC-TTL
-        set beresp.http.X-VC-TTL = "24";
-        set beresp.ttl = std.duration(beresp.http.X-VC-TTL + "h", 0s);
-        set beresp.grace = 2m;
-    }
-}
-

--- a/varnish-conf/lib/xforward.vcl
+++ /dev/null
@@ -1,17 +1,1 @@
-# xforward.vcl -- X-Forwarded-For HTTP Headers
 
-# This should generally be loaded first to make sure that the headers
-# get set appropriately for all requests.  Note that when using this
-# you MUST NOT fall through to the VCL default handler for vcl_recv
-# since that will run the code again, resulting in the client.ip
-# being added twice.
-
-sub vcl_recv {
-    if (req.http.X-Forwarded-For) {
-        set req.http.X-Forwarded-For =
-            req.http.X-Forwarded-For + ", " + client.ip;
-    } else {
-        set req.http.X-Forwarded-For = client.ip;
-    }
-}
-

--- /dev/null
+++ b/varnish-conf/v3/LICENSE
@@ -1,1 +1,340 @@
-
+                    GNU GENERAL PUBLIC LICENSE
+                       Version 2, June 1991
+
+ Copyright (C) 1989, 1991 Free Software Foundation, Inc.,
+ 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301 USA
+ Everyone is permitted to copy and distribute verbatim copies
+ of this license document, but changing it is not allowed.
+
+                            Preamble
+
+  The licenses for most software are designed to take away your
+freedom to share and change it.  By contrast, the GNU General Public
+License is intended to guarantee your freedom to share and change free
+software--to make sure the software is free for all its users.  This
+General Public License applies to most of the Free Software
+Foundation's software and to any other program whose authors commit to
+using it.  (Some other Free Software Foundation software is covered by
+the GNU Lesser General Public License instead.)  You can apply it to
+your programs, too.
+
+  When we speak of free software, we are referring to freedom, not
+price.  Our General Public Licenses are designed to make sure that you
+have the freedom to distribute copies of free software (and charge for
+this service if you wish), that you receive source code or can get it
+if you want it, that you can change the software or use pieces of it
+in new free programs; and that you know you can do these things.
+
+  To protect your rights, we need to make restrictions that forbid
+anyone to deny you these rights or to ask you to surrender the rights.
+These restrictions translate to certain responsibilities for you if you
+distribute copies of the software, or if you modify it.
+
+  For example, if you distribute copies of such a program, whether
+gratis or for a fee, you must give the recipients all the rights that
+you have.  You must make sure that they, too, receive or can get the
+source code.  And you must show them these terms so they know their
+rights.
+
+  We protect your rights with two steps: (1) copyright the software, and
+(2) offer you this license which gives you legal permission to copy,
+distribute and/or modify the software.
+
+  Also, for each author's protection and ours, we want to make certain
+that everyone understands that there is no warranty for this free
+software.  If the software is modified by someone else and passed on, we
+want its recipients to know that what they have is not the original, so
+that any problems introduced by others will not reflect on the original
+authors' reputations.
+
+  Finally, any free program is threatened constantly by software
+patents.  We wish to avoid the danger that redistributors of a free
+program will individually obtain patent licenses, in effect making the
+program proprietary.  To prevent this, we have made it clear that any
+patent must be licensed for everyone's free use or not licensed at all.
+
+  The precise terms and conditions for copying, distribution and
+modification follow.
+
+                    GNU GENERAL PUBLIC LICENSE
+   TERMS AND CONDITIONS FOR COPYING, DISTRIBUTION AND MODIFICATION
+
+  0. This License applies to any program or other work which contains
+a notice placed by the copyright holder saying it may be distributed
+under the terms of this General Public License.  The "Program", below,
+refers to any such program or work, and a "work based on the Program"
+means either the Program or any derivative work under copyright law:
+that is to say, a work containing the Program or a portion of it,
+either verbatim or with modifications and/or translated into another
+language.  (Hereinafter, translation is included without limitation in
+the term "modification".)  Each licensee is addressed as "you".
+
+Activities other than copying, distribution and modification are not
+covered by this License; they are outside its scope.  The act of
+running the Program is not restricted, and the output from the Program
+is covered only if its contents constitute a work based on the
+Program (independent of having been made by running the Program).
+Whether that is true depends on what the Program does.
+
+  1. You may copy and distribute verbatim copies of the Program's
+source code as you receive it, in any medium, provided that you
+conspicuously and appropriately publish on each copy an appropriate
+copyright notice and disclaimer of warranty; keep intact all the
+notices that refer to this License and to the absence of any warranty;
+and give any other recipients of the Program a copy of this License
+along with the Program.
+
+You may charge a fee for the physical act of transferring a copy, and
+you may at your option offer warranty protection in exchange for a fee.
+
+  2. You may modify your copy or copies of the Program or any portion
+of it, thus forming a work based on the Program, and copy and
+distribute such modifications or work under the terms of Section 1
+above, provided that you also meet all of these conditions:
+
+    a) You must cause the modified files to carry prominent notices
+    stating that you changed the files and the date of any change.
+
+    b) You must cause any work that you distribute or publish, that in
+    whole or in part contains or is derived from the Program or any
+    part thereof, to be licensed as a whole at no charge to all third
+    parties under the terms of this License.
+
+    c) If the modified program normally reads commands interactively
+    when run, you must cause it, when started running for such
+    interactive use in the most ordinary way, to print or display an
+    announcement including an appropriate copyright notice and a
+    notice that there is no warranty (or else, saying that you provide
+    a warranty) and that users may redistribute the program under
+    these conditions, and telling the user how to view a copy of this
+    License.  (Exception: if the Program itself is interactive but
+    does not normally print such an announcement, your work based on
+    the Program is not required to print an announcement.)
+
+These requirements apply to the modified work as a whole.  If
+identifiable sections of that work are not derived from the Program,
+and can be reasonably considered independent and separate works in
+themselves, then this License, and its terms, do not apply to those
+sections when you distribute them as separate works.  But when you
+distribute the same sections as part of a whole which is a work based
+on the Program, the distribution of the whole must be on the terms of
+this License, whose permissions for other licensees extend to the
+entire whole, and thus to each and every part regardless of who wrote it.
+
+Thus, it is not the intent of this section to claim rights or contest
+your rights to work written entirely by you; rather, the intent is to
+exercise the right to control the distribution of derivative or
+collective works based on the Program.
+
+In addition, mere aggregation of another work not based on the Program
+with the Program (or with a work based on the Program) on a volume of
+a storage or distribution medium does not bring the other work under
+the scope of this License.
+
+  3. You may copy and distribute the Program (or a work based on it,
+under Section 2) in object code or executable form under the terms of
+Sections 1 and 2 above provided that you also do one of the following:
+
+    a) Accompany it with the complete corresponding machine-readable
+    source code, which must be distributed under the terms of Sections
+    1 and 2 above on a medium customarily used for software interchange; or,
+
+    b) Accompany it with a written offer, valid for at least three
+    years, to give any third party, for a charge no more than your
+    cost of physically performing source distribution, a complete
+    machine-readable copy of the corresponding source code, to be
+    distributed under the terms of Sections 1 and 2 above on a medium
+    customarily used for software interchange; or,
+
+    c) Accompany it with the information you received as to the offer
+    to distribute corresponding source code.  (This alternative is
+    allowed only for noncommercial distribution and only if you
+    received the program in object code or executable form with such
+    an offer, in accord with Subsection b above.)
+
+The source code for a work means the preferred form of the work for
+making modifications to it.  For an executable work, complete source
+code means all the source code for all modules it contains, plus any
+associated interface definition files, plus the scripts used to
+control compilation and installation of the executable.  However, as a
+special exception, the source code distributed need not include
+anything that is normally distributed (in either source or binary
+form) with the major components (compiler, kernel, and so on) of the
+operating system on which the executable runs, unless that component
+itself accompanies the executable.
+
+If distribution of executable or object code is made by offering
+access to copy from a designated place, then offering equivalent
+access to copy the source code from the same place counts as
+distribution of the source code, even though third parties are not
+compelled to copy the source along with the object code.
+
+  4. You may not copy, modify, sublicense, or distribute the Program
+except as expressly provided under this License.  Any attempt
+otherwise to copy, modify, sublicense or distribute the Program is
+void, and will automatically terminate your rights under this License.
+However, parties who have received copies, or rights, from you under
+this License will not have their licenses terminated so long as such
+parties remain in full compliance.
+
+  5. You are not required to accept this License, since you have not
+signed it.  However, nothing else grants you permission to modify or
+distribute the Program or its derivative works.  These actions are
+prohibited by law if you do not accept this License.  Therefore, by
+modifying or distributing the Program (or any work based on the
+Program), you indicate your acceptance of this License to do so, and
+all its terms and conditions for copying, distributing or modifying
+the Program or works based on it.
+
+  6. Each time you redistribute the Program (or any work based on the
+Program), the recipient automatically receives a license from the
+original licensor to copy, distribute or modify the Program subject to
+these terms and conditions.  You may not impose any further
+restrictions on the recipients' exercise of the rights granted herein.
+You are not responsible for enforcing compliance by third parties to
+this License.
+
+  7. If, as a consequence of a court judgment or allegation of patent
+infringement or for any other reason (not limited to patent issues),
+conditions are imposed on you (whether by court order, agreement or
+otherwise) that contradict the conditions of this License, they do not
+excuse you from the conditions of this License.  If you cannot
+distribute so as to satisfy simultaneously your obligations under this
+License and any other pertinent obligations, then as a consequence you
+may not distribute the Program at all.  For example, if a patent
+license would not permit royalty-free redistribution of the Program by
+all those who receive copies directly or indirectly through you, then
+the only way you could satisfy both it and this License would be to
+refrain entirely from distribution of the Program.
+
+If any portion of this section is held invalid or unenforceable under
+any particular circumstance, the balance of the section is intended to
+apply and the section as a whole is intended to apply in other
+circumstances.
+
+It is not the purpose of this section to induce you to infringe any
+patents or other property right claims or to contest validity of any
+such claims; this section has the sole purpose of protecting the
+integrity of the free software distribution system, which is
+implemented by public license practices.  Many people have made
+generous contributions to the wide range of software distributed
+through that system in reliance on consistent application of that
+system; it is up to the author/donor to decide if he or she is willing
+to distribute software through any other system and a licensee cannot
+impose that choice.
+
+This section is intended to make thoroughly clear what is believed to
+be a consequence of the rest of this License.
+
+  8. If the distribution and/or use of the Program is restricted in
+certain countries either by patents or by copyrighted interfaces, the
+original copyright holder who places the Program under this License
+may add an explicit geographical distribution limitation excluding
+those countries, so that distribution is permitted only in or among
+countries not thus excluded.  In such case, this License incorporates
+the limitation as if written in the body of this License.
+
+  9. The Free Software Foundation may publish revised and/or new versions
+of the General Public License from time to time.  Such new versions will
+be similar in spirit to the present version, but may differ in detail to
+address new problems or concerns.
+
+Each version is given a distinguishing version number.  If the Program
+specifies a version number of this License which applies to it and "any
+later version", you have the option of following the terms and conditions
+either of that version or of any later version published by the Free
+Software Foundation.  If the Program does not specify a version number of
+this License, you may choose any version ever published by the Free Software
+Foundation.
+
+  10. If you wish to incorporate parts of the Program into other free
+programs whose distribution conditions are different, write to the author
+to ask for permission.  For software which is copyrighted by the Free
+Software Foundation, write to the Free Software Foundation; we sometimes
+make exceptions for this.  Our decision will be guided by the two goals
+of preserving the free status of all derivatives of our free software and
+of promoting the sharing and reuse of software generally.
+
+                            NO WARRANTY
+
+  11. BECAUSE THE PROGRAM IS LICENSED FREE OF CHARGE, THERE IS NO WARRANTY
+FOR THE PROGRAM, TO THE EXTENT PERMITTED BY APPLICABLE LAW.  EXCEPT WHEN
+OTHERWISE STATED IN WRITING THE COPYRIGHT HOLDERS AND/OR OTHER PARTIES
+PROVIDE THE PROGRAM "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED
+OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF
+MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE.  THE ENTIRE RISK AS
+TO THE QUALITY AND PERFORMANCE OF THE PROGRAM IS WITH YOU.  SHOULD THE
+PROGRAM PROVE DEFECTIVE, YOU ASSUME THE COST OF ALL NECESSARY SERVICING,
+REPAIR OR CORRECTION.
+
+  12. IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING
+WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MAY MODIFY AND/OR
+REDISTRIBUTE THE PROGRAM AS PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES,
+INCLUDING ANY GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING
+OUT OF THE USE OR INABILITY TO USE THE PROGRAM (INCLUDING BUT NOT LIMITED
+TO LOSS OF DATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY
+YOU OR THIRD PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER
+PROGRAMS), EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE
+POSSIBILITY OF SUCH DAMAGES.
+
+                     END OF TERMS AND CONDITIONS
+
+            How to Apply These Terms to Your New Programs
+
+  If you develop a new program, and you want it to be of the greatest
+possible use to the public, the best way to achieve this is to make it
+free software which everyone can redistribute and change under these terms.
+
+  To do so, attach the following notices to the program.  It is safest
+to attach them to the start of each source file to most effectively
+convey the exclusion of warranty; and each file should have at least
+the "copyright" line and a pointer to where the full notice is found.
+
+    <one line to give the program's name and a brief idea of what it does.>
+    Copyright (C) <year>  <name of author>
+
+    This program is free software; you can redistribute it and/or modify
+    it under the terms of the GNU General Public License as published by
+    the Free Software Foundation; either version 2 of the License, or
+    (at your option) any later version.
+
+    This program is distributed in the hope that it will be useful,
+    but WITHOUT ANY WARRANTY; without even the implied warranty of
+    MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
+    GNU General Public License for more details.
+
+    You should have received a copy of the GNU General Public License along
+    with this program; if not, write to the Free Software Foundation, Inc.,
+    51 Franklin Street, Fifth Floor, Boston, MA 02110-1301 USA.
+
+Also add information on how to contact you by electronic and paper mail.
+
+If the program is interactive, make it output a short notice like this
+when it starts in an interactive mode:
+
+    Gnomovision version 69, Copyright (C) year name of author
+    Gnomovision comes with ABSOLUTELY NO WARRANTY; for details type `show w'.
+    This is free software, and you are welcome to redistribute it
+    under certain conditions; type `show c' for details.
+
+The hypothetical commands `show w' and `show c' should show the appropriate
+parts of the General Public License.  Of course, the commands you use may
+be called something other than `show w' and `show c'; they could even be
+mouse-clicks or menu items--whatever suits your program.
+
+You should also get your employer (if you work as a programmer) or your
+school, if any, to sign a "copyright disclaimer" for the program, if
+necessary.  Here is a sample; alter the names:
+
+  Yoyodyne, Inc., hereby disclaims all copyright interest in the program
+  `Gnomovision' (which makes passes at compilers) written by James Hacker.
+
+  <signature of Ty Coon>, 1 April 1989
+  Ty Coon, President of Vice
+
+This General Public License does not permit incorporating your program into
+proprietary programs.  If your program is a subroutine library, you may
+consider it more useful to permit linking proprietary applications with the
+library.  If this is what you want to do, use the GNU Lesser General
+Public License instead of this License.
+

--- /dev/null
+++ b/varnish-conf/v3/README.rst
@@ -1,1 +1,149 @@
+======================
+varnish-vcl-collection
+======================
 
+Collection of Varnish VCL files.  The purpose of this collection is to make
+it easier to configure varnish for some common setups and behaviors.  Some
+of these files require you to define specific ACLs in your main VCL, and also
+note that the order of including files could change the behavior of Varnish.
+
+The main goal for this VCL Collection is to provide a simple config with just
+a few options that can make Varnish work for the majority of sites. Most of
+the "configuration" is done by choosing which files to include and defining
+ACLs. We hope to provide a robust configuration that can be used with
+relatively little information or control over what is actually running on
+the backend.  This is particularly useful for managed web hosts who want
+to have customers benefit from the performance of a caching proxy without
+limiting what can run on the web backend and without customizing the
+configuration for each customer.
+
+See `default.vcl` for an example of how to use this collection
+of VCLs to configure Varnish for a WordPress site.
+
+
+CloudFlare
+==========
+
+If you use CloudFlare and the backend is running `mod_cloudflare` (for Apache)
+or `http_realip_module` (for Nginx), then you should use `lib/cloudflare.vcl`.
+
+CloudFlare uses the HTTP Header `CF-Connecting-IP` to store the original
+client IP address.  Note that unlike the `X-Forwarded-For` Header, this just
+contains the original IP address, not the entire forward chain.
+
+If you are using a CloudFlare Railgun server, or have any other trusted proxy
+servers between Varnish and CloudFlare, you will need to specify them in the
+`cloudflare` ACL.
+
+Also note that you will need to make sure that Varnish's IP is configured
+as trusted in `mod_cloudflare` or the `http_realip_module` on the backend.
+
+Example usage::
+
+	include "lib/cloudflare.vcl";
+
+	acl cloudflare {
+		# put the IP of your Railgun (or proxy) server here
+		# "1.2.3.4";
+	}
+
+
+Mobile Device Optimizaiton
+==========================
+
+Different applications optimize for mobile devices in different ways.  The
+best way is to use an "adaptive" design so that the same HTML is served to
+both desktop and mobile devices.  If your application is "adaptive", then
+no special Varnish config is necessary; all devices will access the same
+objects in the Varnish cache.
+
+However, if your application does serve different content to different
+devices, then you'll need to handle that in Varnish.  Since applications
+do mobile device detection differently, the VCL code included here is
+intentionally limited and simple.  Crafting a custom configuration to handle
+the way your application treats mobile devices will usually give better
+results than using one of the following standard configs.
+
+`lib/mobile_cache.vcl` simply adds the string `mobile` to the hash data to
+give mobile devices a separate cache from non-mobile devices.  This is only
+viable if your application serves just 2 different versions of each page
+depending on if the visitor is on a mobile device or not (and if the
+application uses the same method to detect mobile devices).  Any disagreement
+between `mobile_cache.vcl` and your backend on what User-Agents should be
+considered "mobile" could mean that the incorrect versions of pages are
+served to some visitors.
+
+`lib/mobile_pass.vcl` simply disables caching for mobile devices.  This is
+not good for performance, but will at least will prevent serving the
+incorrect version of pages to mobile visitors.
+
+
+HTTP Purging
+============
+
+Include `lib/purge.vcl` to allow purging pages from the cache using the HTTP
+PURGE method.  This uses the ban feature of varnish and will make bans take
+advantage of Varnish's ban-lurker.  You will need to specify a `purge` ACL
+so that only requests coming from your application are allowed to purge.
+
+Example usage::
+
+	include "lib/purge.vcl";
+
+	acl purge {
+		# include the IP of your app if it isn't on localhost
+		"localhost";
+		"127.0.0.1";
+	}
+
+There are several different possible behaviors of HTTP purging which can be
+controlled with the X-VC-Purge-Method HTTP header.  This config will be smart
+and attempt to automatically pick the best method based on the URL if you
+don't use an X-VC-Purge-Method header.  See the comments in `lib/purge.vcl` for
+details.
+You can also use the X-VC-Purge-Key method. Generate a MD5/SHA-256 hash and fill it on line
+if (req.http.X-VC-Purge-Key == "hash-to-be-filled-in") {
+in lib/purge.vcl. Then use the same hash in Varnish Caching WP admin.
+
+
+Static File Caching
+===================
+
+Include `lib/static.vcl` to use a simple set of rules to cache static files.
+This will ignore the query string part of request URLs, and discard all
+cookies for these requests.  This will also cache static files for 24 hours.
+
+The cache behavior for this vcl can be bypassed by adding `nocache` to the
+url.  For example, `http://example.com/foo.jpg?nocache` will always
+retrieve the file from the backend instead of serving from the cache.
+
+
+Big Files
+=========
+
+Varnish cannot cache files larger than the entire cache.  Additionally, a few
+large files could potentially fill up the cache and force many more small
+files to be removed from the cache. Use `lib/bigfiles.vcl` or
+`lib/bigfiles_pipe.vcl` to prevent caching files larger than 10 MB.  This
+size was chosen because this should allow most common website assets to be
+cached.  Files larger than 10 MB such as videos, long podcasts, or binary
+downloads are better suited to be served with a CDN or some server separate
+from your main web application.  This config will still allow Varnish to
+serve these large files, but the files will always be retrieved from the
+backend.
+
+`lib/bigfiles.vcl` marks files with `hit_for_pass` when they are above the
+size threshold.  However this only works in Varnish 3.0.3 or later.  Earlier
+versions of Varnish will instead show an internal server error when this
+method is used.  In the case of these older versions of Varnish, you should
+use `lib/bigfiles_pipe.vcl`, which instead pipes the request.
+
+Your main VCL must have `import std;`.  This import line is not included
+within the files themselves because having an import multiple times in a
+Varnish config (counting all included files) produces a compile error.
+
+Example usage::
+
+	import std;
+	include "lib/bigfiles.vcl";
+

--- /dev/null
+++ b/varnish-conf/v3/conf/acl.vcl
@@ -1,1 +1,10 @@
+acl cloudflare {
+    # set this ip to your Railgun IP (if applicable)
+    # "1.2.3.4";
+}
 
+acl purge {
+    "localhost";
+    "127.0.0.1";
+    #"192.168.0.2";
+}

--- /dev/null
+++ b/varnish-conf/v3/conf/backend.vcl
@@ -1,1 +1,14 @@
+backend backend1 {
+    .host = "192.168.0.2";
+    .port = "80";
+}
 
+director backends round-robin {
+    {
+        .backend = backend1;
+    }
+}
+
+sub vcl_recv {
+    set req.backend = backends;
+}

--- /dev/null
+++ b/varnish-conf/v3/default.vcl
@@ -1,1 +1,159 @@
+include "conf/backend.vcl";
+include "conf/acl.vcl";
 
+import std;
+
+include "lib/xforward.vcl";
+include "lib/cloudflare.vcl";
+include "lib/purge.vcl";
+include "lib/bigfiles.vcl";
+include "lib/static.vcl";
+
+# Pick just one of the following:
+# (or don't use either of these if your application is "adaptive")
+# include "lib/mobile_cache.vcl";
+# include "lib/mobile_pass.vcl";
+
+### WordPress-specific config ###
+sub vcl_recv {
+    # pipe on weird http methods
+    if (req.request !~ "^GET|HEAD|PUT|POST|TRACE|OPTIONS|DELETE$") {
+        return(pipe);
+    }
+
+    # redirect yourdomain.com to www.yourdomain.com
+    #if (req.http.host ~ "^yourdomain\.com$") {
+    #    error 750 "http://www.yourdomain.com" + req.url;
+    #}
+
+    # if you use a subdomain for admin section, do not cache it
+    #if (req.http.host ~ "admin.yourdomain.com") {
+    #    set req.http.X-VC-Cacheable = "NO:Admin domain";
+    #    return(pass);
+    #}
+
+    ### Check for reasons to bypass the cache!
+    # never cache anything except GET/HEAD
+    if (req.request != "GET" && req.request != "HEAD") {
+        set req.http.X-VC-Cacheable = "NO:Request method:" + req.request;
+        return(pass);
+    }
+
+    # don't cache logged-in users. you can set users `logged in cookie` name in settings
+    if (req.http.Cookie ~ "c005492c65") {
+        set req.http.X-VC-Cacheable = "NO:Found logged in cookie";
+        return(pass);
+    }
+
+    # don't cache ajax requests
+    if (req.http.X-Requested-With == "XMLHttpRequest") {
+        set req.http.X-VC-Cacheable = "NO:Requested with: XMLHttpRequest";
+        return(pass);
+    }
+
+    # don't cache these special pages. Not needed, left here as example
+    #if (req.url ~ "nocache|wp-admin|wp-(comments-post|login|activate|mail)\.php|bb-admin|server-status|control\.php|bb-login\.php|bb-reset-password\.php|register\.php") {
+    #    set req.http.X-VC-Cacheable = "NO:Special page: " + req.url;
+    #    return(pass);
+    #}
+
+    ### looks like we might actually cache it!
+    # fix up the request
+    set req.grace = 2m;
+    set req.url = regsub(req.url, "\?replytocom=.*$", "");
+
+    # strip query parameters from all urls (so they cache as a single object)
+    # be carefull using this option
+    #if (req.url ~ "\?.*") {
+    #    set req.url = regsub(req.url, "\?.*", "");
+    #}
+
+    # Remove has_js, Google Analytics __*, and wooTracker cookies.
+    set req.http.Cookie = regsuball(req.http.Cookie, "(^|;\s*)(__[a-z]+|has_js|wooTracker)=[^;]*", "");
+    set req.http.Cookie = regsub(req.http.Cookie, "^;\s*", "");
+    if (req.http.Cookie ~ "^\s*$") {
+        unset req.http.Cookie;
+    }
+
+    return(lookup);
+}
+
+sub vcl_hash {
+    set req.http.hash = req.url;
+    if (req.http.host) {
+        set req.http.hash = req.http.hash + "#" + req.http.host;
+    } else {
+        set req.http.hash = req.http.hash + "#" + server.ip;
+    }
+    # Add the browser cookie only if a WordPress cookie found. Not needed, left here as example
+    #if (req.http.Cookie ~ "wp-postpass_|wordpress_logged_in_|comment_author|PHPSESSID") {
+    #    hash_data(req.http.Cookie);
+    #    set req.http.hash = req.http.hash + "#" + req.http.Cookie;
+    #}
+}
+
+sub vcl_fetch {
+    # make sure grace is at least 2 minutes
+    if (beresp.grace < 2m) {
+        set beresp.grace = 2m;
+    }
+
+    # overwrite ttl with X-VC-TTL
+    if (beresp.http.X-VC-TTL) {
+        set beresp.ttl = std.duration(beresp.http.X-VC-TTL + "s", 0s);
+    }
+
+    # catch obvious reasons we can't cache
+    if (beresp.http.Set-Cookie) {
+        set beresp.ttl = 0s;
+    }
+
+    # Don't cache object as instructed by header bereq.X-VC-Cacheable
+    if (req.http.X-VC-Cacheable ~ "^NO") {
+        set beresp.http.X-VC-Cacheable = req.http.X-VC-Cacheable;
+        return(hit_for_pass);
+
+    # Varnish determined the object was not cacheable
+    } else if (beresp.ttl <= 0s) {
+        if (!beresp.http.X-VC-Cacheable) {
+            set beresp.http.X-VC-Cacheable = "NO:Not cacheable, ttl: "+ beresp.ttl;
+        }
+        return(hit_for_pass);
+
+    # You are respecting the Cache-Control=private header from the backend
+    } else if (beresp.http.Cache-Control ~ "private") {
+        set beresp.http.X-VC-Cacheable = "NO:Cache-Control=private";
+        return(hit_for_pass);
+
+    # Cache object
+    } else if (beresp.http.X-VC-Enabled ~ "true") {
+        if (!beresp.http.X-VC-Cacheable) {
+            set beresp.http.X-VC-Cacheable = "YES:Is cacheable, ttl: " + beresp.ttl;
+        }
+
+    # Do not cache object
+    } else if (beresp.http.X-VC-Enabled ~ "false") {
+        if (!beresp.http.X-VC-Cacheable) {
+            set beresp.http.X-VC-Cacheable = "NO:Disabled";
+        }
+        set beresp.ttl = 0s;
+    }
+
+    # Avoid caching error responses
+    if (beresp.status == 404 || beresp.status >= 500) {
+        set beresp.ttl   = 0s;
+        set beresp.grace = 15s;
+    }
+
+    # Deliver the content
+    return(deliver);
+}
+
+sub vcl_error {
+    if (obj.status == 750) {
+        set obj.http.Location = obj.response;
+        set obj.status = 302;
+        return(deliver);
+    }
+}
+

--- /dev/null
+++ b/varnish-conf/v3/lib/bigfiles.vcl
@@ -1,1 +1,9 @@
+# bigfiles.vcl -- Bypass Cache for Large Files
 
+sub vcl_fetch {
+    # Bypass cache for files > 10 MB
+    if (std.integer(beresp.http.Content-Length, 0) > 10485760) {
+        return (hit_for_pass);
+    }
+}
+

--- /dev/null
+++ b/varnish-conf/v3/lib/bigfiles_pipe.vcl
@@ -1,1 +1,23 @@
+# bigfiles_pipe.vcl -- Pipe for Large Files
 
+# You must have "import std;" in your main vcl:
+# import std;
+
+# NOTE: Using restart and pipe is a workaround for a bug in varnish prior to
+# 3.0.3.  In 3.0.3+, hit_for_pass in vcl_fetch is all that is necessary.
+
+sub vcl_recv {
+    if (req.http.X-Pipe-Big-File && req.restarts > 0) {
+        unset req.http.X-Pipe-Big-File;
+        return (pipe);
+    }
+}
+
+sub vcl_fetch {
+    # Bypass cache for files > 10 MB
+    if (std.integer(beresp.http.Content-Length, 0) > 10485760) {
+        set req.http.X-Pipe-Big-File = "Yes";
+        return (restart);
+    }
+}
+

--- /dev/null
+++ b/varnish-conf/v3/lib/cloudflare.vcl
@@ -1,1 +1,41 @@
+# cloudflare.vcl -- CloudFlare HTTP Headers
 
+# This should generally be loaded first to make sure that the headers
+# get set appropriately for all requests.
+
+acl official_cloudflare {
+    # https://www.cloudflare.com/ips-v4
+    "204.93.240.0"/24;
+    "204.93.177.0"/24;
+    "199.27.128.0"/21;
+    "173.245.48.0"/20;
+    "103.21.244.0"/22;
+    "103.22.200.0"/22;
+    "103.31.4.0"/22;
+    "141.101.64.0"/18;
+    "108.162.192.0"/18;
+    "190.93.240.0"/20;
+    "188.114.96.0"/20;
+    "197.234.240.0"/22;
+    "198.41.128.0"/17;
+    "162.158.0.0"/15;
+    # https://www.cloudflare.com/ips-v6
+    "2400:cb00::"/32;
+    "2606:4700::"/32;
+    "2803:f800::"/32;
+    "2405:b500::"/32;
+    "2405:8100::"/32;
+}
+
+sub vcl_recv {
+    # Set the CF-Connecting-IP header
+    # If the client.ip is trusted, we leave the header alone if present.
+    if (req.http.CF-Connecting-IP) {
+        if (client.ip !~ official_cloudflare && client.ip !~ cloudflare) {
+            set req.http.CF-Connecting-IP = client.ip;
+        }
+    } else {
+        set req.http.CF-Connecting-IP = client.ip;
+    }
+}
+

--- /dev/null
+++ b/varnish-conf/v3/lib/mobile_cache.vcl
@@ -1,1 +1,20 @@
+# mobile_cache.vcl -- Separate cache for mobile clients
 
+# If the User-Agent looks like a mobile device, then we add the string
+# "mobile" to the hash_data.  This results in mobile devices having
+# a separate cache from non-mobile devices.
+#
+# Note that if the backend does anything more sophisticated than having
+# a "desktop" and a "mobile" version of pages (for example serving one
+# page to iPhones and another to Androids), this will not be desirable.
+# Also if the backend disagrees with this logic as far as what is a
+# "mobile" User-Agent, then we may save the wrong version of pages in
+# the cache.
+
+sub vcl_hash {
+    # General User-Agent list (anything that remotely looks like a mobile device)
+    if (req.http.User-Agent ~ "(?i)ipod|android|blackberry|phone|mobile|kindle|silk|fennec|tablet|webos|palm|windows ce|nokia|philips|samsung|sanyo|sony|panasonic|ericsson|alcatel|series60|series40|opera mini|opera mobi|au-mic|audiovox|avantgo|blazer|danger|docomo|epoc|ericy|i-mode|ipaq|midp-|mot-|netfront|nitro|pocket|portalmmm|rover|sie-|symbian|cldc-|j2me|up\.browser|up\.link|vodafone|wap1\.|wap2\.") {
+        hash_data("mobile");
+    }
+}
+

--- /dev/null
+++ b/varnish-conf/v3/lib/mobile_pass.vcl
@@ -1,1 +1,22 @@
+# mobile_pass.vcl -- Mobile pass-through support for Varnish
 
+# This simply bypasses the cache for anything that looks like a mobile
+# (or tablet) device.
+# Also passes through some requests that are specifically for the WordPress
+# Jetpack mobile plugin.
+
+sub vcl_recv {
+    # Rules specifically for the Jetpack Mobile module
+    if (req.url ~ "\?(.*&)?(ak_action|app-download)=") {
+        return(pass);
+    }
+    if (req.http.Cookie ~ "(^|;\s*)akm_mobile=") {
+        return(pass);
+    }
+
+    # General User-Agent blacklist (anything that remotely looks like a mobile device)
+    if (req.http.User-Agent ~ "(?i)ipod|android|blackberry|phone|mobile|kindle|silk|fennec|tablet|webos|palm|windows ce|nokia|philips|samsung|sanyo|sony|panasonic|ericsson|alcatel|series60|series40|opera mini|opera mobi|au-mic|audiovox|avantgo|blazer|danger|docomo|epoc|ericy|i-mode|ipaq|midp-|mot-|netfront|nitro|pocket|portalmmm|rover|sie-|symbian|cldc-|j2me|up\.browser|up\.link|vodafone|wap1\.|wap2\.") {
+        return(pass);
+    }
+}
+

--- /dev/null
+++ b/varnish-conf/v3/lib/purge.vcl
@@ -1,1 +1,106 @@
+# purge.vcl -- Cache Purge Library for Varnish
 
+# Regex purging
+# Treat the request URL as a regular expression.
+sub purge_regex {
+    ban("obj.http.X-VC-Req-URL ~ " + req.url + " && obj.http.X-VC-Req-Host == " + req.http.host);
+}
+
+# Exact purging
+# Use the exact request URL (including any query params)
+sub purge_exact {
+    ban("obj.http.X-VC-Req-URL == " + req.url + " && obj.http.X-VC-Req-Host == " + req.http.host);
+}
+
+# Page purging (default)
+# Use the exact request URL, but ignore any query params
+sub purge_page {
+    set req.url = regsub(req.url, "\?.*$", "");
+    ban("obj.http.X-VC-Req-URL-Base == " + req.url + " && obj.http.X-VC-Req-Host == " + req.http.host);
+}
+
+# The purge behavior can be controlled with the X-VC-Purge-Method header.
+#
+# Setting the X-VC-Purge-Method header to contain "regex" or "exact" will use
+# those respective behaviors.  Any other value for the X-Purge header will
+# use the default ("page") behavior.
+#
+# The X-VC-Purge-Method header is not case-sensitive.
+#
+# If no X-VC-Purge-Method header is set, the request url is inspected to attempt
+# a best guess as to what purge behavior is expected.  This should work for
+# most cases, although if you want to guarantee some behavior you should
+# always set the X-VC-Purge-Method header.
+
+sub vcl_recv {
+    set req.http.X-VC-My-Purge-Key = "ff93c3cb929cee86901c7eefc8088e9511c005492c6502a930360c02221cf8f4";
+    if (req.request == "PURGE") {
+        if (req.http.X-VC-Purge-Key == req.http.X-VC-My-Purge-Key) {
+            set req.http.X-VC-Purge-Key-Auth = "true";
+        } else {
+            set req.http.X-VC-Purge-Key-Auth = "false";
+        }
+        if (client.ip !~ purge && req.http.X-VC-Purge-Key-Auth != "true") {
+            error 405 "Not allowed from " + client.ip;
+        }
+
+        if (req.http.X-VC-Purge-Method) {
+            if (req.http.X-VC-Purge-Method ~ "(?i)regex") {
+                call purge_regex;
+            } elsif (req.http.X-VC-Purge-Method ~ "(?i)exact") {
+                call purge_exact;
+            } else {
+                call purge_page;
+            }
+        } else {
+            # No X-VC-Purge-Method header was specified.
+            # Do our best to figure out which one they want.
+            if (req.url ~ "\.\*" || req.url ~ "^\^" || req.url ~ "\$$" || req.url ~ "\\[.?*+^$|()]") {
+                call purge_regex;
+            } elsif (req.url ~ "\?") {
+                call purge_exact;
+            } else {
+                call purge_page;
+            }
+        }
+        error 200 "Purged " + req.url + " " + req.http.host;
+    }
+    unset req.http.X-VC-My-Purge-Key;
+    # unset Varnish Caching custom headers from client
+    unset req.http.X-VC-Cacheable;
+    unset req.http.X-VC-Debug;
+}
+
+sub vcl_fetch {
+    set beresp.http.X-VC-Req-Host = req.http.host;
+    set beresp.http.X-VC-Req-URL = req.url;
+    set beresp.http.X-VC-Req-URL-Base = regsub(req.url, "\?.*$", "");
+}
+
+sub vcl_deliver {
+    unset resp.http.X-VC-Req-Host;
+    unset resp.http.X-VC-Req-URL;
+    unset resp.http.X-VC-Req-URL-Base;
+
+    if (obj.hits > 0) {
+        set resp.http.X-VC-Cache = "HIT";
+    } else {
+        set resp.http.X-VC-Cache = "MISS";
+    }
+
+    if (req.http.X-VC-Debug ~ "true" || resp.http.X-VC-Debug ~ "true") {
+        set resp.http.X-VC-Hash = req.http.hash;
+        if (req.http.X-VC-DebugMessage) {
+            set resp.http.X-VC-DebugMessage = req.http.X-VC-DebugMessage;
+        }
+    } else {
+        unset resp.http.X-VC-Enabled;
+        unset resp.http.X-VC-Cache;
+        unset resp.http.X-VC-Debug;
+        unset resp.http.X-VC-DebugMessage;
+        unset resp.http.X-VC-Cacheable;
+        unset resp.http.X-VC-Purge-Key-Auth;
+        unset resp.http.X-VC-TTL;
+    }
+}
+

--- /dev/null
+++ b/varnish-conf/v3/lib/static.vcl
@@ -1,1 +1,38 @@
+# static.vcl -- Static File Caching for Varnish
 
+sub vcl_recv {
+    if (req.request ~ "^(GET|HEAD)$" && req.url ~ "\.(jpg|jpeg|gif|png|ico|css|zip|tgz|gz|rar|bz2|pdf|txt|tar|wav|bmp|rtf|js|flv|swf|html|htm)(\?.*)?$") {
+        # if you use a subdomain for admin section, do not cache it
+        #if (req.http.host ~ "admin.yourdomain.com") {
+        #    set req.http.X-VC-Cacheable = "NO:Admin domain";
+        #    return(pass);
+        #}
+        # enable this if you want
+        #if (req.url ~ "debug") {
+        #    set req.http.X-VC-Debug = "true";
+        #}
+        # enable this if you need it
+        #if (req.url ~ "nocache") {
+        #    set req.http.X-VC-Cacheable = "NO:Not cacheable, nocache in URL";
+        #    return(pass);
+        #}
+        set req.url = regsub(req.url, "\?.*$", "");
+        # unset cookie only if no http auth
+        if (!req.http.Authorization) {
+            unset req.http.Cookie;
+        }
+        set req.grace = 2m;
+        return(lookup);
+    }
+}
+
+sub vcl_fetch {
+    if (req.request ~ "^(GET|HEAD)$" && req.url ~ "\.(jpg|jpeg|gif|png|ico|css|zip|tgz|gz|rar|bz2|pdf|txt|tar|wav|bmp|rtf|js|flv|swf|html|htm)$") {
+        # overwrite ttl with X-VC-TTL
+        set beresp.http.X-VC-TTL = 24*60*60;
+        set beresp.ttl = std.duration(beresp.http.X-VC-TTL + "s", 0s);
+        set beresp.http.X-VC-Cacheable = "YES:Is cacheable, ttl: " + beresp.ttl;
+        set beresp.grace = 2m;
+    }
+}
+

--- /dev/null
+++ b/varnish-conf/v3/lib/xforward.vcl
@@ -1,1 +1,17 @@
+# xforward.vcl -- X-Forwarded-For HTTP Headers
 
+# This should generally be loaded first to make sure that the headers
+# get set appropriately for all requests.  Note that when using this
+# you MUST NOT fall through to the VCL default handler for vcl_recv
+# since that will run the code again, resulting in the client.ip
+# being added twice.
+
+sub vcl_recv {
+    if (req.http.X-Forwarded-For) {
+        set req.http.X-Forwarded-For =
+            req.http.X-Forwarded-For + ", " + client.ip;
+    } else {
+        set req.http.X-Forwarded-For = client.ip;
+    }
+}
+

--- /dev/null
+++ b/varnish-conf/v4/LICENSE
@@ -1,1 +1,340 @@
-
+                    GNU GENERAL PUBLIC LICENSE
+                       Version 2, June 1991
+
+ Copyright (C) 1989, 1991 Free Software Foundation, Inc.,
+ 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301 USA
+ Everyone is permitted to copy and distribute verbatim copies
+ of this license document, but changing it is not allowed.
+
+                            Preamble
+
+  The licenses for most software are designed to take away your
+freedom to share and change it.  By contrast, the GNU General Public
+License is intended to guarantee your freedom to share and change free
+software--to make sure the software is free for all its users.  This
+General Public License applies to most of the Free Software
+Foundation's software and to any other program whose authors commit to
+using it.  (Some other Free Software Foundation software is covered by
+the GNU Lesser General Public License instead.)  You can apply it to
+your programs, too.
+
+  When we speak of free software, we are referring to freedom, not
+price.  Our General Public Licenses are designed to make sure that you
+have the freedom to distribute copies of free software (and charge for
+this service if you wish), that you receive source code or can get it
+if you want it, that you can change the software or use pieces of it
+in new free programs; and that you know you can do these things.
+
+  To protect your rights, we need to make restrictions that forbid
+anyone to deny you these rights or to ask you to surrender the rights.
+These restrictions translate to certain responsibilities for you if you
+distribute copies of the software, or if you modify it.
+
+  For example, if you distribute copies of such a program, whether
+gratis or for a fee, you must give the recipients all the rights that
+you have.  You must make sure that they, too, receive or can get the
+source code.  And you must show them these terms so they know their
+rights.
+
+  We protect your rights with two steps: (1) copyright the software, and
+(2) offer you this license which gives you legal permission to copy,
+distribute and/or modify the software.
+
+  Also, for each author's protection and ours, we want to make certain
+that everyone understands that there is no warranty for this free
+software.  If the software is modified by someone else and passed on, we
+want its recipients to know that what they have is not the original, so
+that any problems introduced by others will not reflect on the original
+authors' reputations.
+
+  Finally, any free program is threatened constantly by software
+patents.  We wish to avoid the danger that redistributors of a free
+program will individually obtain patent licenses, in effect making the
+program proprietary.  To prevent this, we have made it clear that any
+patent must be licensed for everyone's free use or not licensed at all.
+
+  The precise terms and conditions for copying, distribution and
+modification follow.
+
+                    GNU GENERAL PUBLIC LICENSE
+   TERMS AND CONDITIONS FOR COPYING, DISTRIBUTION AND MODIFICATION
+
+  0. This License applies to any program or other work which contains
+a notice placed by the copyright holder saying it may be distributed
+under the terms of this General Public License.  The "Program", below,
+refers to any such program or work, and a "work based on the Program"
+means either the Program or any derivative work under copyright law:
+that is to say, a work containing the Program or a portion of it,
+either verbatim or with modifications and/or translated into another
+language.  (Hereinafter, translation is included without limitation in
+the term "modification".)  Each licensee is addressed as "you".
+
+Activities other than copying, distribution and modification are not
+covered by this License; they are outside its scope.  The act of
+running the Program is not restricted, and the output from the Program
+is covered only if its contents constitute a work based on the
+Program (independent of having been made by running the Program).
+Whether that is true depends on what the Program does.
+
+  1. You may copy and distribute verbatim copies of the Program's
+source code as you receive it, in any medium, provided that you
+conspicuously and appropriately publish on each copy an appropriate
+copyright notice and disclaimer of warranty; keep intact all the
+notices that refer to this License and to the absence of any warranty;
+and give any other recipients of the Program a copy of this License
+along with the Program.
+
+You may charge a fee for the physical act of transferring a copy, and
+you may at your option offer warranty protection in exchange for a fee.
+
+  2. You may modify your copy or copies of the Program or any portion
+of it, thus forming a work based on the Program, and copy and
+distribute such modifications or work under the terms of Section 1
+above, provided that you also meet all of these conditions:
+
+    a) You must cause the modified files to carry prominent notices
+    stating that you changed the files and the date of any change.
+
+    b) You must cause any work that you distribute or publish, that in
+    whole or in part contains or is derived from the Program or any
+    part thereof, to be licensed as a whole at no charge to all third
+    parties under the terms of this License.
+
+    c) If the modified program normally reads commands interactively
+    when run, you must cause it, when started running for such
+    interactive use in the most ordinary way, to print or display an
+    announcement including an appropriate copyright notice and a
+    notice that there is no warranty (or else, saying that you provide
+    a warranty) and that users may redistribute the program under
+    these conditions, and telling the user how to view a copy of this
+    License.  (Exception: if the Program itself is interactive but
+    does not normally print such an announcement, your work based on
+    the Program is not required to print an announcement.)
+
+These requirements apply to the modified work as a whole.  If
+identifiable sections of that work are not derived from the Program,
+and can be reasonably considered independent and separate works in
+themselves, then this License, and its terms, do not apply to those
+sections when you distribute them as separate works.  But when you
+distribute the same sections as part of a whole which is a work based
+on the Program, the distribution of the whole must be on the terms of
+this License, whose permissions for other licensees extend to the
+entire whole, and thus to each and every part regardless of who wrote it.
+
+Thus, it is not the intent of this section to claim rights or contest
+your rights to work written entirely by you; rather, the intent is to
+exercise the right to control the distribution of derivative or
+collective works based on the Program.
+
+In addition, mere aggregation of another work not based on the Program
+with the Program (or with a work based on the Program) on a volume of
+a storage or distribution medium does not bring the other work under
+the scope of this License.
+
+  3. You may copy and distribute the Program (or a work based on it,
+under Section 2) in object code or executable form under the terms of
+Sections 1 and 2 above provided that you also do one of the following:
+
+    a) Accompany it with the complete corresponding machine-readable
+    source code, which must be distributed under the terms of Sections
+    1 and 2 above on a medium customarily used for software interchange; or,
+
+    b) Accompany it with a written offer, valid for at least three
+    years, to give any third party, for a charge no more than your
+    cost of physically performing source distribution, a complete
+    machine-readable copy of the corresponding source code, to be
+    distributed under the terms of Sections 1 and 2 above on a medium
+    customarily used for software interchange; or,
+
+    c) Accompany it with the information you received as to the offer
+    to distribute corresponding source code.  (This alternative is
+    allowed only for noncommercial distribution and only if you
+    received the program in object code or executable form with such
+    an offer, in accord with Subsection b above.)
+
+The source code for a work means the preferred form of the work for
+making modifications to it.  For an executable work, complete source
+code means all the source code for all modules it contains, plus any
+associated interface definition files, plus the scripts used to
+control compilation and installation of the executable.  However, as a
+special exception, the source code distributed need not include
+anything that is normally distributed (in either source or binary
+form) with the major components (compiler, kernel, and so on) of the
+operating system on which the executable runs, unless that component
+itself accompanies the executable.
+
+If distribution of executable or object code is made by offering
+access to copy from a designated place, then offering equivalent
+access to copy the source code from the same place counts as
+distribution of the source code, even though third parties are not
+compelled to copy the source along with the object code.
+
+  4. You may not copy, modify, sublicense, or distribute the Program
+except as expressly provided under this License.  Any attempt
+otherwise to copy, modify, sublicense or distribute the Program is
+void, and will automatically terminate your rights under this License.
+However, parties who have received copies, or rights, from you under
+this License will not have their licenses terminated so long as such
+parties remain in full compliance.
+
+  5. You are not required to accept this License, since you have not
+signed it.  However, nothing else grants you permission to modify or
+distribute the Program or its derivative works.  These actions are
+prohibited by law if you do not accept this License.  Therefore, by
+modifying or distributing the Program (or any work based on the
+Program), you indicate your acceptance of this License to do so, and
+all its terms and conditions for copying, distributing or modifying
+the Program or works based on it.
+
+  6. Each time you redistribute the Program (or any work based on the
+Program), the recipient automatically receives a license from the
+original licensor to copy, distribute or modify the Program subject to
+these terms and conditions.  You may not impose any further
+restrictions on the recipients' exercise of the rights granted herein.
+You are not responsible for enforcing compliance by third parties to
+this License.
+
+  7. If, as a consequence of a court judgment or allegation of patent
+infringement or for any other reason (not limited to patent issues),
+conditions are imposed on you (whether by court order, agreement or
+otherwise) that contradict the conditions of this License, they do not
+excuse you from the conditions of this License.  If you cannot
+distribute so as to satisfy simultaneously your obligations under this
+License and any other pertinent obligations, then as a consequence you
+may not distribute the Program at all.  For example, if a patent
+license would not permit royalty-free redistribution of the Program by
+all those who receive copies directly or indirectly through you, then
+the only way you could satisfy both it and this License would be to
+refrain entirely from distribution of the Program.
+
+If any portion of this section is held invalid or unenforceable under
+any particular circumstance, the balance of the section is intended to
+apply and the section as a whole is intended to apply in other
+circumstances.
+
+It is not the purpose of this section to induce you to infringe any
+patents or other property right claims or to contest validity of any
+such claims; this section has the sole purpose of protecting the
+integrity of the free software distribution system, which is
+implemented by public license practices.  Many people have made
+generous contributions to the wide range of software distributed
+through that system in reliance on consistent application of that
+system; it is up to the author/donor to decide if he or she is willing
+to distribute software through any other system and a licensee cannot
+impose that choice.
+
+This section is intended to make thoroughly clear what is believed to
+be a consequence of the rest of this License.
+
+  8. If the distribution and/or use of the Program is restricted in
+certain countries either by patents or by copyrighted interfaces, the
+original copyright holder who places the Program under this License
+may add an explicit geographical distribution limitation excluding
+those countries, so that distribution is permitted only in or among
+countries not thus excluded.  In such case, this License incorporates
+the limitation as if written in the body of this License.
+
+  9. The Free Software Foundation may publish revised and/or new versions
+of the General Public License from time to time.  Such new versions will
+be similar in spirit to the present version, but may differ in detail to
+address new problems or concerns.
+
+Each version is given a distinguishing version number.  If the Program
+specifies a version number of this License which applies to it and "any
+later version", you have the option of following the terms and conditions
+either of that version or of any later version published by the Free
+Software Foundation.  If the Program does not specify a version number of
+this License, you may choose any version ever published by the Free Software
+Foundation.
+
+  10. If you wish to incorporate parts of the Program into other free
+programs whose distribution conditions are different, write to the author
+to ask for permission.  For software which is copyrighted by the Free
+Software Foundation, write to the Free Software Foundation; we sometimes
+make exceptions for this.  Our decision will be guided by the two goals
+of preserving the free status of all derivatives of our free software and
+of promoting the sharing and reuse of software generally.
+
+                            NO WARRANTY
+
+  11. BECAUSE THE PROGRAM IS LICENSED FREE OF CHARGE, THERE IS NO WARRANTY
+FOR THE PROGRAM, TO THE EXTENT PERMITTED BY APPLICABLE LAW.  EXCEPT WHEN
+OTHERWISE STATED IN WRITING THE COPYRIGHT HOLDERS AND/OR OTHER PARTIES
+PROVIDE THE PROGRAM "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED
+OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF
+MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE.  THE ENTIRE RISK AS
+TO THE QUALITY AND PERFORMANCE OF THE PROGRAM IS WITH YOU.  SHOULD THE
+PROGRAM PROVE DEFECTIVE, YOU ASSUME THE COST OF ALL NECESSARY SERVICING,
+REPAIR OR CORRECTION.
+
+  12. IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING
+WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MAY MODIFY AND/OR
+REDISTRIBUTE THE PROGRAM AS PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES,
+INCLUDING ANY GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING
+OUT OF THE USE OR INABILITY TO USE THE PROGRAM (INCLUDING BUT NOT LIMITED
+TO LOSS OF DATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY
+YOU OR THIRD PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER
+PROGRAMS), EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE
+POSSIBILITY OF SUCH DAMAGES.
+
+                     END OF TERMS AND CONDITIONS
+
+            How to Apply These Terms to Your New Programs
+
+  If you develop a new program, and you want it to be of the greatest
+possible use to the public, the best way to achieve this is to make it
+free software which everyone can redistribute and change under these terms.
+
+  To do so, attach the following notices to the program.  It is safest
+to attach them to the start of each source file to most effectively
+convey the exclusion of warranty; and each file should have at least
+the "copyright" line and a pointer to where the full notice is found.
+
+    <one line to give the program's name and a brief idea of what it does.>
+    Copyright (C) <year>  <name of author>
+
+    This program is free software; you can redistribute it and/or modify
+    it under the terms of the GNU General Public License as published by
+    the Free Software Foundation; either version 2 of the License, or
+    (at your option) any later version.
+
+    This program is distributed in the hope that it will be useful,
+    but WITHOUT ANY WARRANTY; without even the implied warranty of
+    MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
+    GNU General Public License for more details.
+
+    You should have received a copy of the GNU General Public License along
+    with this program; if not, write to the Free Software Foundation, Inc.,
+    51 Franklin Street, Fifth Floor, Boston, MA 02110-1301 USA.
+
+Also add information on how to contact you by electronic and paper mail.
+
+If the program is interactive, make it output a short notice like this
+when it starts in an interactive mode:
+
+    Gnomovision version 69, Copyright (C) year name of author
+    Gnomovision comes with ABSOLUTELY NO WARRANTY; for details type `show w'.
+    This is free software, and you are welcome to redistribute it
+    under certain conditions; type `show c' for details.
+
+The hypothetical commands `show w' and `show c' should show the appropriate
+parts of the General Public License.  Of course, the commands you use may
+be called something other than `show w' and `show c'; they could even be
+mouse-clicks or menu items--whatever suits your program.
+
+You should also get your employer (if you work as a programmer) or your
+school, if any, to sign a "copyright disclaimer" for the program, if
+necessary.  Here is a sample; alter the names:
+
+  Yoyodyne, Inc., hereby disclaims all copyright interest in the program
+  `Gnomovision' (which makes passes at compilers) written by James Hacker.
+
+  <signature of Ty Coon>, 1 April 1989
+  Ty Coon, President of Vice
+
+This General Public License does not permit incorporating your program into
+proprietary programs.  If your program is a subroutine library, you may
+consider it more useful to permit linking proprietary applications with the
+library.  If this is what you want to do, use the GNU Lesser General
+Public License instead of this License.
+

--- /dev/null
+++ b/varnish-conf/v4/README.rst
@@ -1,1 +1,149 @@
+======================
+varnish-vcl-collection
+======================
 
+Collection of Varnish VCL files.  The purpose of this collection is to make
+it easier to configure varnish for some common setups and behaviors.  Some
+of these files require you to define specific ACLs in your main VCL, and also
+note that the order of including files could change the behavior of Varnish.
+
+The main goal for this VCL Collection is to provide a simple config with just
+a few options that can make Varnish work for the majority of sites. Most of
+the "configuration" is done by choosing which files to include and defining
+ACLs. We hope to provide a robust configuration that can be used with
+relatively little information or control over what is actually running on
+the backend.  This is particularly useful for managed web hosts who want
+to have customers benefit from the performance of a caching proxy without
+limiting what can run on the web backend and without customizing the
+configuration for each customer.
+
+See `default.vcl` for an example of how to use this collection
+of VCLs to configure Varnish for a WordPress site.
+
+
+CloudFlare
+==========
+
+If you use CloudFlare and the backend is running `mod_cloudflare` (for Apache)
+or `http_realip_module` (for Nginx), then you should use `lib/cloudflare.vcl`.
+
+CloudFlare uses the HTTP Header `CF-Connecting-IP` to store the original
+client IP address.  Note that unlike the `X-Forwarded-For` Header, this just
+contains the original IP address, not the entire forward chain.
+
+If you are using a CloudFlare Railgun server, or have any other trusted proxy
+servers between Varnish and CloudFlare, you will need to specify them in the
+`cloudflare` ACL.
+
+Also note that you will need to make sure that Varnish's IP is configured
+as trusted in `mod_cloudflare` or the `http_realip_module` on the backend.
+
+Example usage::
+
+	include "lib/cloudflare.vcl";
+
+	acl cloudflare {
+		# put the IP of your Railgun (or proxy) server here
+		# "1.2.3.4";
+	}
+
+
+Mobile Device Optimizaiton
+==========================
+
+Different applications optimize for mobile devices in different ways.  The
+best way is to use an "adaptive" design so that the same HTML is served to
+both desktop and mobile devices.  If your application is "adaptive", then
+no special Varnish config is necessary; all devices will access the same
+objects in the Varnish cache.
+
+However, if your application does serve different content to different
+devices, then you'll need to handle that in Varnish.  Since applications
+do mobile device detection differently, the VCL code included here is
+intentionally limited and simple.  Crafting a custom configuration to handle
+the way your application treats mobile devices will usually give better
+results than using one of the following standard configs.
+
+`lib/mobile_cache.vcl` simply adds the string `mobile` to the hash data to
+give mobile devices a separate cache from non-mobile devices.  This is only
+viable if your application serves just 2 different versions of each page
+depending on if the visitor is on a mobile device or not (and if the
+application uses the same method to detect mobile devices).  Any disagreement
+between `mobile_cache.vcl` and your backend on what User-Agents should be
+considered "mobile" could mean that the incorrect versions of pages are
+served to some visitors.
+
+`lib/mobile_pass.vcl` simply disables caching for mobile devices.  This is
+not good for performance, but will at least will prevent serving the
+incorrect version of pages to mobile visitors.
+
+
+HTTP Purging
+============
+
+Include `lib/purge.vcl` to allow purging pages from the cache using the HTTP
+PURGE method.  This uses the ban feature of varnish and will make bans take
+advantage of Varnish's ban-lurker.  You will need to specify a `purge` ACL
+so that only requests coming from your application are allowed to purge.
+
+Example usage::
+
+	include "lib/purge.vcl";
+
+	acl purge {
+		# include the IP of your app if it isn't on localhost
+		"localhost";
+		"127.0.0.1";
+	}
+
+There are several different possible behaviors of HTTP purging which can be
+controlled with the X-VC-Purge-Method HTTP header.  This config will be smart
+and attempt to automatically pick the best method based on the URL if you
+don't use an X-VC-Purge-Method header.  See the comments in `lib/purge.vcl` for
+details.
+You can also use the X-VC-Purge-Key method. Generate a MD5/SHA-256 hash and fill it on line
+if (req.http.X-VC-Purge-Key == "hash-to-be-filled-in") {
+in lib/purge.vcl. Then use the same hash in Varnish Caching WP admin.
+
+
+Static File Caching
+===================
+
+Include `lib/static.vcl` to use a simple set of rules to cache static files.
+This will ignore the query string part of request URLs, and discard all
+cookies for these requests.  This will also cache static files for 24 hours.
+
+The cache behavior for this vcl can be bypassed by adding `nocache` to the
+url.  For example, `http://example.com/foo.jpg?nocache` will always
+retrieve the file from the backend instead of serving from the cache.
+
+
+Big Files
+=========
+
+Varnish cannot cache files larger than the entire cache.  Additionally, a few
+large files could potentially fill up the cache and force many more small
+files to be removed from the cache. Use `lib/bigfiles.vcl` or
+`lib/bigfiles_pipe.vcl` to prevent caching files larger than 10 MB.  This
+size was chosen because this should allow most common website assets to be
+cached.  Files larger than 10 MB such as videos, long podcasts, or binary
+downloads are better suited to be served with a CDN or some server separate
+from your main web application.  This config will still allow Varnish to
+serve these large files, but the files will always be retrieved from the
+backend.
+
+`lib/bigfiles.vcl` marks files with `hit_for_pass` when they are above the
+size threshold.  However this only works in Varnish 3.0.3 or later.  Earlier
+versions of Varnish will instead show an internal server error when this
+method is used.  In the case of these older versions of Varnish, you should
+use `lib/bigfiles_pipe.vcl`, which instead pipes the request.
+
+Your main VCL must have `import std;`.  This import line is not included
+within the files themselves because having an import multiple times in a
+Varnish config (counting all included files) produces a compile error.
+
+Example usage::
+
+	import std;
+	include "lib/bigfiles.vcl";
+

--- /dev/null
+++ b/varnish-conf/v4/conf/acl.vcl
@@ -1,1 +1,10 @@
+acl cloudflare {
+    # set this ip to your Railgun IP (if applicable)
+    # "1.2.3.4";
+}
 
+acl purge {
+    "localhost";
+    "127.0.0.1";
+    #"192.168.0.2";
+}

--- /dev/null
+++ b/varnish-conf/v4/conf/backend.vcl
@@ -1,1 +1,16 @@
+import directors;
 
+backend backend1 {
+    .host = "192.168.0.2";
+    .port = "80";
+}
+
+sub vcl_init {
+    new backends = directors.round_robin();
+    backends.add_backend(backend1);
+}
+
+sub vcl_recv {
+    set req.backend_hint = backends.backend();
+}
+

--- /dev/null
+++ b/varnish-conf/v4/default.vcl
@@ -1,1 +1,164 @@
+vcl 4.0;
 
+include "conf/backend.vcl";
+include "conf/acl.vcl";
+
+import std;
+
+include "lib/xforward.vcl";
+include "lib/cloudflare.vcl";
+include "lib/purge.vcl";
+include "lib/bigfiles.vcl";
+include "lib/static.vcl";
+
+# Pick just one of the following:
+# (or don't use either of these if your application is "adaptive")
+# include "lib/mobile_cache.vcl";
+# include "lib/mobile_pass.vcl";
+
+### WordPress-specific config ###
+sub vcl_recv {
+    # pipe on weird http methods
+    if (req.method !~ "^GET|HEAD|PUT|POST|TRACE|OPTIONS|DELETE$") {
+        return(pipe);
+    }
+
+    # redirect yourdomain.com to www.yourdomain.com
+    #if (req.http.host ~ "^yourdomain\.com$") {
+    #    set req.http.X-VC-Redirect = "http://www.yourdomain.com" + req.url;
+    #    return (synth(750, "Moved permanently"));
+    #}
+
+    # if you use a subdomain for admin section, do not cache it
+    #if (req.http.host ~ "admin.yourdomain.com") {
+    #    set req.http.X-VC-Cacheable = "NO:Admin domain";
+    #    return(pass);
+    #}
+
+    ### Check for reasons to bypass the cache!
+    # never cache anything except GET/HEAD
+    if (req.method != "GET" && req.method != "HEAD") {
+        set req.http.X-VC-Cacheable = "NO:Request method:" + req.method;
+        return(pass);
+    }
+
+    # don't cache logged-in users. you can set users `logged in cookie` name in settings
+    if (req.http.Cookie ~ "c005492c65") {
+        set req.http.X-VC-Cacheable = "NO:Found logged in cookie";
+        return(pass);
+    }
+
+    # don't cache ajax requests
+    if (req.http.X-Requested-With == "XMLHttpRequest") {
+        set req.http.X-VC-Cacheable = "NO:Requested with: XMLHttpRequest";
+        return(pass);
+    }
+
+    # don't cache these special pages. Not needed, left here as example
+    #if (req.url ~ "nocache|wp-admin|wp-(comments-post|login|activate|mail)\.php|bb-admin|server-status|control\.php|bb-login\.php|bb-reset-password\.php|register\.php") {
+    #    set req.http.X-VC-Cacheable = "NO:Special page: " + req.url;
+    #    return(pass);
+    #}
+
+    ### looks like we might actually cache it!
+    # fix up the request
+    set req.url = regsub(req.url, "\?replytocom=.*$", "");
+
+    # strip query parameters from all urls (so they cache as a single object)
+    # be carefull using this option
+    #if (req.url ~ "\?.*") {
+    #    set req.url = regsub(req.url, "\?.*", "");
+    #}
+
+    # Remove has_js, Google Analytics __*, and wooTracker cookies.
+    set req.http.Cookie = regsuball(req.http.Cookie, "(^|;\s*)(__[a-z]+|has_js|wooTracker)=[^;]*", "");
+    set req.http.Cookie = regsub(req.http.Cookie, "^;\s*", "");
+    if (req.http.Cookie ~ "^\s*$") {
+        unset req.http.Cookie;
+    }
+
+    return(hash);
+}
+
+sub vcl_hash {
+    set req.http.hash = req.url;
+    if (req.http.host) {
+        set req.http.hash = req.http.hash + "#" + req.http.host;
+    } else {
+        set req.http.hash = req.http.hash + "#" + server.ip;
+    }
+    # Add the browser cookie only if cookie found. Not needed, left here as example
+    #if (req.http.Cookie ~ "wp-postpass_|wordpress_logged_in_|comment_author|PHPSESSID") {
+    #    hash_data(req.http.Cookie);
+    #    set req.http.hash = req.http.hash + "#" + req.http.Cookie;
+    #}
+}
+
+sub vcl_backend_response {
+    # make sure grace is at least 2 minutes
+    if (beresp.grace < 2m) {
+        set beresp.grace = 2m;
+    }
+
+    # overwrite ttl with X-VC-TTL
+    if (beresp.http.X-VC-TTL) {
+        set beresp.ttl = std.duration(beresp.http.X-VC-TTL + "s", 0s);
+    }
+
+    # catch obvious reasons we can't cache
+    if (beresp.http.Set-Cookie) {
+        set beresp.ttl = 0s;
+    }
+
+    # Don't cache object as instructed by header bereq.X-VC-Cacheable
+    if (bereq.http.X-VC-Cacheable ~ "^NO") {
+        set beresp.http.X-VC-Cacheable = bereq.http.X-VC-Cacheable;
+        set beresp.uncacheable = true;
+        set beresp.ttl = 120s;
+
+    # Varnish determined the object is not cacheable
+    } else if (beresp.ttl <= 0s) {
+        if (!beresp.http.X-VC-Cacheable) {
+            set beresp.http.X-VC-Cacheable = "NO:Not cacheable, ttl: "+ beresp.ttl;
+        }
+        set beresp.uncacheable = true;
+        set beresp.ttl = 120s;
+
+    # You are respecting the Cache-Control=private header from the backend
+    } else if (beresp.http.Cache-Control ~ "private") {
+        set beresp.http.X-VC-Cacheable = "NO:Cache-Control=private";
+        set beresp.uncacheable = true;
+        set beresp.ttl = 120s;
+
+    # Cache object
+    } else if (beresp.http.X-VC-Enabled ~ "true") {
+        if (!beresp.http.X-VC-Cacheable) {
+            set beresp.http.X-VC-Cacheable = "YES:Is cacheable, ttl: " + beresp.ttl;
+        }
+
+    # Do not cache object
+    } else if (beresp.http.X-VC-Enabled ~ "false") {
+        if (!beresp.http.X-VC-Cacheable) {
+            set beresp.http.X-VC-Cacheable = "NO:Disabled";
+        }
+        set beresp.ttl = 0s;
+    }
+
+    # Avoid caching error responses
+    if (beresp.status == 404 || beresp.status >= 500) {
+        set beresp.ttl   = 0s;
+        set beresp.grace = 15s;
+    }
+
+    # Deliver the content
+    return(deliver);
+}
+
+sub vcl_synth {
+    if (resp.status == 750) {
+        set resp.http.Location = req.http.X-VC-Redirect;
+        set resp.status = 302;
+        return(deliver);
+    }
+}
+

--- /dev/null
+++ b/varnish-conf/v4/lib/bigfiles.vcl
@@ -1,1 +1,11 @@
+# bigfiles.vcl -- Bypass Cache for Large Files
 
+sub vcl_backend_response {
+    # Bypass cache for files > 10 MB
+    if (std.integer(beresp.http.Content-Length, 0) > 10485760) {
+        set beresp.uncacheable = true;
+        set beresp.ttl = 120s;
+        return (deliver);
+    }
+}
+

--- /dev/null
+++ b/varnish-conf/v4/lib/bigfiles_pipe.vcl
@@ -1,1 +1,23 @@
+# bigfiles_pipe.vcl -- Pipe for Large Files
 
+# You must have "import std;" in your main vcl:
+# import std;
+
+# NOTE: Using restart and pipe is a workaround for a bug in varnish prior to
+# 3.0.3.  In 3.0.3+, hit_for_pass in vcl_fetch is all that is necessary.
+
+sub vcl_recv {
+    if (req.http.X-Pipe-Big-File && req.restarts > 0) {
+        unset req.http.X-Pipe-Big-File;
+        return (pipe);
+    }
+}
+
+sub vcl_fetch {
+    # Bypass cache for files > 10 MB
+    if (std.integer(beresp.http.Content-Length, 0) > 10485760) {
+        set req.http.X-Pipe-Big-File = "Yes";
+        return (restart);
+    }
+}
+

--- /dev/null
+++ b/varnish-conf/v4/lib/cloudflare.vcl
@@ -1,1 +1,41 @@
+# cloudflare.vcl -- CloudFlare HTTP Headers
 
+# This should generally be loaded first to make sure that the headers
+# get set appropriately for all requests.
+
+acl official_cloudflare {
+    # https://www.cloudflare.com/ips-v4
+    "204.93.240.0"/24;
+    "204.93.177.0"/24;
+    "199.27.128.0"/21;
+    "173.245.48.0"/20;
+    "103.21.244.0"/22;
+    "103.22.200.0"/22;
+    "103.31.4.0"/22;
+    "141.101.64.0"/18;
+    "108.162.192.0"/18;
+    "190.93.240.0"/20;
+    "188.114.96.0"/20;
+    "197.234.240.0"/22;
+    "198.41.128.0"/17;
+    "162.158.0.0"/15;
+    # https://www.cloudflare.com/ips-v6
+    "2400:cb00::"/32;
+    "2606:4700::"/32;
+    "2803:f800::"/32;
+    "2405:b500::"/32;
+    "2405:8100::"/32;
+}
+
+sub vcl_recv {
+    # Set the CF-Connecting-IP header
+    # If the client.ip is trusted, we leave the header alone if present.
+    if (req.http.CF-Connecting-IP) {
+        if (client.ip !~ official_cloudflare && client.ip !~ cloudflare) {
+            set req.http.CF-Connecting-IP = client.ip;
+        }
+    } else {
+        set req.http.CF-Connecting-IP = client.ip;
+    }
+}
+

--- /dev/null
+++ b/varnish-conf/v4/lib/mobile_cache.vcl
@@ -1,1 +1,20 @@
+# mobile_cache.vcl -- Separate cache for mobile clients
 
+# If the User-Agent looks like a mobile device, then we add the string
+# "mobile" to the hash_data.  This results in mobile devices having
+# a separate cache from non-mobile devices.
+#
+# Note that if the backend does anything more sophisticated than having
+# a "desktop" and a "mobile" version of pages (for example serving one
+# page to iPhones and another to Androids), this will not be desirable.
+# Also if the backend disagrees with this logic as far as what is a
+# "mobile" User-Agent, then we may save the wrong version of pages in
+# the cache.
+
+sub vcl_hash {
+    # General User-Agent list (anything that remotely looks like a mobile device)
+    if (req.http.User-Agent ~ "(?i)ipod|android|blackberry|phone|mobile|kindle|silk|fennec|tablet|webos|palm|windows ce|nokia|philips|samsung|sanyo|sony|panasonic|ericsson|alcatel|series60|series40|opera mini|opera mobi|au-mic|audiovox|avantgo|blazer|danger|docomo|epoc|ericy|i-mode|ipaq|midp-|mot-|netfront|nitro|pocket|portalmmm|rover|sie-|symbian|cldc-|j2me|up\.browser|up\.link|vodafone|wap1\.|wap2\.") {
+        hash_data("mobile");
+    }
+}
+

--- /dev/null
+++ b/varnish-conf/v4/lib/mobile_pass.vcl
@@ -1,1 +1,22 @@
+# mobile_pass.vcl -- Mobile pass-through support for Varnish
 
+# This simply bypasses the cache for anything that looks like a mobile
+# (or tablet) device.
+# Also passes through some requests that are specifically for the WordPress
+# Jetpack mobile plugin.
+
+sub vcl_recv {
+    # Rules specifically for the Jetpack Mobile module
+    if (req.url ~ "\?(.*&)?(ak_action|app-download)=") {
+        return(pass);
+    }
+    if (req.http.Cookie ~ "(^|;\s*)akm_mobile=") {
+        return(pass);
+    }
+
+    # General User-Agent blacklist (anything that remotely looks like a mobile device)
+    if (req.http.User-Agent ~ "(?i)ipod|android|blackberry|phone|mobile|kindle|silk|fennec|tablet|webos|palm|windows ce|nokia|philips|samsung|sanyo|sony|panasonic|ericsson|alcatel|series60|series40|opera mini|opera mobi|au-mic|audiovox|avantgo|blazer|danger|docomo|epoc|ericy|i-mode|ipaq|midp-|mot-|netfront|nitro|pocket|portalmmm|rover|sie-|symbian|cldc-|j2me|up\.browser|up\.link|vodafone|wap1\.|wap2\.") {
+        return(pass);
+    }
+}
+

--- /dev/null
+++ b/varnish-conf/v4/lib/purge.vcl
@@ -1,1 +1,106 @@
+# purge.vcl -- Cache Purge Library for Varnish
 
+# Regex purging
+# Treat the request URL as a regular expression.
+sub purge_regex {
+    ban("obj.http.X-VC-Req-URL ~ " + req.url + " && obj.http.X-VC-Req-Host == " + req.http.host);
+}
+
+# Exact purging
+# Use the exact request URL (including any query params)
+sub purge_exact {
+    ban("obj.http.X-VC-Req-URL == " + req.url + " && obj.http.X-VC-Req-Host == " + req.http.host);
+}
+
+# Page purging (default)
+# Use the exact request URL, but ignore any query params
+sub purge_page {
+    set req.url = regsub(req.url, "\?.*$", "");
+    ban("obj.http.X-VC-Req-URL-Base == " + req.url + " && obj.http.X-VC-Req-Host == " + req.http.host);
+}
+
+# The purge behavior can be controlled with the X-VC-Purge-Method header.
+#
+# Setting the X-VC-Purge-Method header to contain "regex" or "exact" will use
+# those respective behaviors.  Any other value for the X-Purge header will
+# use the default ("page") behavior.
+#
+# The X-VC-Purge-Method header is not case-sensitive.
+#
+# If no X-VC-Purge-Method header is set, the request url is inspected to attempt
+# a best guess as to what purge behavior is expected.  This should work for
+# most cases, although if you want to guarantee some behavior you should
+# always set the X-VC-Purge-Method header.
+
+sub vcl_recv {
+    set req.http.X-VC-My-Purge-Key = "ff93c3cb929cee86901c7eefc8088e9511c005492c6502a930360c02221cf8f4";
+    if (req.method == "PURGE") {
+        if (req.http.X-VC-Purge-Key == req.http.X-VC-My-Purge-Key) {
+            set req.http.X-VC-Purge-Key-Auth = "true";
+        } else {
+            set req.http.X-VC-Purge-Key-Auth = "false";
+        }
+        if (client.ip !~ purge && req.http.X-VC-Purge-Key-Auth != "true") {
+            return (synth(405, "Not allowed from " + client.ip));
+        }
+
+        if (req.http.X-VC-Purge-Method) {
+            if (req.http.X-VC-Purge-Method ~ "(?i)regex") {
+                call purge_regex;
+            } elsif (req.http.X-VC-Purge-Method ~ "(?i)exact") {
+                call purge_exact;
+            } else {
+                call purge_page;
+            }
+        } else {
+            # No X-VC-Purge-Method header was specified.
+            # Do our best to figure out which one they want.
+            if (req.url ~ "\.\*" || req.url ~ "^\^" || req.url ~ "\$$" || req.url ~ "\\[.?*+^$|()]") {
+                call purge_regex;
+            } elsif (req.url ~ "\?") {
+                call purge_exact;
+            } else {
+                call purge_page;
+            }
+        }
+        return (synth(200,"Purged " + req.url + " " + req.http.host));
+    }
+    unset req.http.X-VC-My-Purge-Key;
+    # unset Varnish Caching custom headers from client
+    unset req.http.X-VC-Cacheable;
+    unset req.http.X-VC-Debug;
+}
+
+sub vcl_backend_response {
+    set beresp.http.X-VC-Req-Host = bereq.http.host;
+    set beresp.http.X-VC-Req-URL = bereq.url;
+    set beresp.http.X-VC-Req-URL-Base = regsub(bereq.url, "\?.*$", "");
+}
+
+sub vcl_deliver {
+    unset resp.http.X-VC-Req-Host;
+    unset resp.http.X-VC-Req-URL;
+    unset resp.http.X-VC-Req-URL-Base;
+
+    if (obj.hits > 0) {
+        set resp.http.X-VC-Cache = "HIT";
+    } else {
+        set resp.http.X-VC-Cache = "MISS";
+    }
+
+    if (req.http.X-VC-Debug ~ "true" || resp.http.X-VC-Debug ~ "true") {
+        set resp.http.X-VC-Hash = req.http.hash;
+        if (req.http.X-VC-DebugMessage) {
+            set resp.http.X-VC-DebugMessage = req.http.X-VC-DebugMessage;
+        }
+    } else {
+        unset resp.http.X-VC-Enabled;
+        unset resp.http.X-VC-Cache;
+        unset resp.http.X-VC-Debug;
+        unset resp.http.X-VC-DebugMessage;
+        unset resp.http.X-VC-Cacheable;
+        unset resp.http.X-VC-Purge-Key-Auth;
+        unset resp.http.X-VC-TTL;
+    }
+}
+

--- /dev/null
+++ b/varnish-conf/v4/lib/static.vcl
@@ -1,1 +1,36 @@
+# static.vcl -- Static File Caching for Varnish
 
+sub vcl_recv {
+    if (req.method ~ "^(GET|HEAD)$" && req.url ~ "\.(jpg|jpeg|gif|png|ico|css|zip|tgz|gz|rar|bz2|pdf|txt|tar|wav|bmp|rtf|js|flv|swf|html|htm)(\?.*)?$") {
+        # if you use a subdomain for admin section, do not cache it
+        #if (req.http.host ~ "admin.yourdomain.com") {
+        #    set req.http.X-VC-Cacheable = "NO:Admin domain";
+        #    return(pass);
+        #}
+        # enable this if you want
+        #if (req.url ~ "debug") {
+        #    set req.http.X-VC-Debug = "true";
+        #}
+        # enable this if you need it
+        #if (req.url ~ "nocache") {
+        #    set req.http.X-VC-Cacheable = "NO:Not cacheable, nocache in URL";
+        #    return(pass);
+        #}
+        set req.url = regsub(req.url, "\?.*$", "");
+        # unset cookie only if no http auth
+        if (!req.http.Authorization) {
+            unset req.http.Cookie;
+        }
+        return(hash);
+    }
+}
+
+sub vcl_backend_response {
+    if (bereq.method ~ "^(GET|HEAD)$" && bereq.url ~ "\.(jpg|jpeg|gif|png|ico|css|zip|tgz|gz|rar|bz2|pdf|txt|tar|wav|bmp|rtf|js|flv|swf|html|htm)$") {
+        # overwrite ttl with X-VC-TTL
+        set beresp.http.X-VC-TTL = 24*60*60;
+        set beresp.ttl = std.duration(beresp.http.X-VC-TTL + "s", 0s);
+        set beresp.http.X-VC-Cacheable = "YES:Is cacheable, ttl: " + beresp.ttl;
+    }
+}
+

--- /dev/null
+++ b/varnish-conf/v4/lib/xforward.vcl
@@ -1,1 +1,17 @@
+# xforward.vcl -- X-Forwarded-For HTTP Headers
 
+# This should generally be loaded first to make sure that the headers
+# get set appropriately for all requests.  Note that when using this
+# you MUST NOT fall through to the VCL default handler for vcl_recv
+# since that will run the code again, resulting in the client.ip
+# being added twice.
+
+sub vcl_recv {
+    if (req.http.X-Forwarded-For) {
+        set req.http.X-Forwarded-For =
+            req.http.X-Forwarded-For + ", " + client.ip;
+    } else {
+        set req.http.X-Forwarded-For = client.ip;
+    }
+}
+

--- a/vcaching.php
+++ b/vcaching.php
@@ -1,9 +1,9 @@
 <?php
 /*
-Plugin Name: VCaching
+Plugin Name: Varnish Caching
 Plugin URI: http://wordpress.org/extend/plugins/vcaching/
 Description: WordPress Varnish Cache integration.
-Version: 1.2.2
+Version: 1.4.3
 Author: Razvan Stanga
 Author URI: http://git.razvi.ro/
 License: http://www.apache.org/licenses/LICENSE-2.0
@@ -22,12 +22,14 @@
     protected $varnishHost = null;
     protected $dynamicHost = null;
     protected $ipsToHosts = array();
+    protected $statsJsons = array();
     protected $purgeKey = null;
     protected $getParam = 'purge_varnish_cache';
     protected $postTypes = array('page', 'post');
     protected $override = 0;
     protected $customFields = array();
     protected $noticeMessage = '';
+    protected $truncateNotice = false;
     protected $debug = 0;
 
     public function __construct()
@@ -57,15 +59,20 @@
 
     public function init()
     {
-        load_plugin_textdomain($this->plugin);
+        load_plugin_textdomain($this->plugin, false, plugin_basename( dirname( __FILE__ ) ) . '/languages' );
 
         add_action('wp', array($this, 'buffer_start'), 1000000);
         add_action('shutdown', array($this, 'buffer_end'), 1000000);
 
+        $this->truncateNotice = get_option($this->prefix . 'truncate_notice');
         $this->debug = get_option($this->prefix . 'debug');
 
         // send headers to varnish
         add_action('send_headers', array($this, 'send_headers'), 1000000);
+
+        // logged in cookie
+        add_action('wp_login', array($this, 'wp_login'), 1000000);
+        add_action('wp_logout', array($this, 'wp_logout'), 1000000);
 
         // register events to purge post
         foreach ($this->getRegisterEvents() as $event) {
@@ -140,12 +147,15 @@
         $this->varnishIp = get_option($this->prefix . 'ips');
         $this->varnishHost = get_option($this->prefix . 'hosts');
         $this->dynamicHost = get_option($this->prefix . 'dynamic_host');
+        $this->statsJsons = get_option($this->prefix . 'stats_json_file');
         $varnishIp = explode(',', $this->varnishIp);
         $varnishHost = explode(',', $this->varnishHost);
+        $statsJsons = explode(',', $this->statsJsons);
         foreach ($varnishIp as $key => $ip) {
             $this->ipsToHosts[] = array(
                 'ip' => $ip,
-                'host' => $this->dynamicHost ? $_SERVER['HTTP_HOST'] : $varnishHost[$key]
+                'host' => $this->dynamicHost ? $_SERVER['HTTP_HOST'] : $varnishHost[$key],
+                'statsJson' => isset($statsJsons[$key]) ? $statsJsons[$key] : null
             );
         }
     }
@@ -210,7 +220,7 @@
                                 echo '<p><strong>' . $customField['title'] . '</strong></p>';
                                 echo '<label class="screen-reader-text" for="' . $this->prefix . $customField['name'] . '">' . $customField['title'] . '</label>';
                                 echo '<p><input type="checkbox" name="' . $this->prefix . $customField['name'] . '" id="' . $this->prefix . $customField['name'] . '" value="yes"';
-                                if (get_post_meta( $post->ID, $this->prefix . $customField['name'], true ) == "yes")
+                                if (get_post_meta($post->ID, $this->prefix . $customField['name'], true ) == "yes")
                                     echo ' checked="checked"';
                                 echo '" style="width: auto;" /></p>';
                                 break;
@@ -254,13 +264,13 @@
 
     public function purge_varnish_cache_all_adminbar($admin_bar)
     {
-        $admin_bar->add_menu( array(
+        $admin_bar->add_menu(array(
             'id'    => 'purge-all-varnish-cache',
             'title' => __('Purge ALL Varnish Cache', $this->plugin),
             'href'  => wp_nonce_url(add_query_arg($this->getParam, 1), $this->plugin),
             'meta'  => array(
                 'title' => __('Purge ALL Varnish Cache', $this->plugin),
-            ),
+            )
         ));
     }
 
@@ -348,14 +358,19 @@
                     }
                 }
             } else {
-                $this->noticeMessage .= '<br />Trying to purge URL : ' . $purgeme;
-                $message = preg_match("/<title>(.*)<\/title>/i", $response['body'], $matches);
-                $this->noticeMessage .= ' => <br /> ' . isset($matches[1]) ? " => " . $matches[1] : $response['body'];
-                $this->noticeMessage .= '<br />';
-                if ($this->debug) {
-                    $this->noticeMessage .= $response['body'] . "<br />";
+                if ($this->truncateNotice && $key <= 2 || $this->truncateNotice == false) {
+                    $this->noticeMessage .= '' . __('Trying to purge URL :', $this->plugin) . $purgeme;
+                    preg_match("/<title>(.*)<\/title>/i", $response['body'], $matches);
+                    $this->noticeMessage .= ' => <br /> ' . isset($matches[1]) ? " => " . $matches[1] : $response['body'];
+                    $this->noticeMessage .= '<br />';
+                    if ($this->debug) {
+                        $this->noticeMessage .= $response['body'] . "<br />";
+                    }
                 }
             }
+        }
+        if ($this->truncateNotice) {
+            $this->noticeMessage .= '<br />' . __('Truncate message activated. Showing only first 3 messages.', $this->plugin);
         }
 
         do_action('after_purge_url', $url, $purgeme);
@@ -380,21 +395,21 @@
             $categories = get_the_category($postId);
             if ($categories) {
                 foreach ($categories as $cat) {
-                    array_push($listofurls, get_category_link( $cat->term_id));
+                    array_push($listofurls, get_category_link($cat->term_id));
                 }
             }
             // Tag purge based on Donnacha's work in WP Super Cache
             $tags = get_the_tags($postId);
             if ($tags) {
                 foreach ($tags as $tag) {
-                    array_push($listofurls, get_tag_link( $tag->term_id));
+                    array_push($listofurls, get_tag_link($tag->term_id));
                 }
             }
 
             // Author URL
             array_push($listofurls,
-                get_author_posts_url(get_post_field( 'post_author', $postId)),
-                get_author_feed_link(get_post_field( 'post_author', $postId))
+                get_author_posts_url(get_post_field('post_author', $postId)),
+                get_author_feed_link(get_post_field('post_author', $postId))
             );
 
             // Archives and their feeds
@@ -422,16 +437,14 @@
             // Home Page and (if used) posts page
             array_push($listofurls, home_url('/'));
             if ( get_option('show_on_front') == 'page') {
-                array_push($listofurls, get_permalink( get_option('page_for_posts')));
+                array_push($listofurls, get_permalink(get_option('page_for_posts')));
             }
 
             // Now flush all the URLs we've collected
             foreach ($listofurls as $url) {
                 array_push($this->purgeUrls, $url) ;
             }
-
-        }
-
+        }
         // Filter to add or remove urls to the array of purged urls
         // @param array $purgeUrls the urls (paths) to be purged
         // @param int $postId the id of the new/edited post
@@ -444,7 +457,12 @@
         $enable = get_option($this->prefix . 'enable');
         if ($enable) {
             Header('X-VC-Enabled: true', true);
-            $ttl = get_option($this->prefix . 'ttl');
+            if (is_user_logged_in()) {
+                Header('X-VC-Cacheable: NO:User is logged in', true);
+                $ttl = 0;
+            } else {
+                $ttl = get_option($this->prefix . 'ttl');
+            }
             Header('X-VC-TTL: ' . $ttl, true);
             if ($debug = get_option($this->prefix . 'debug')) {
                 Header('X-VC-Debug: true', true);
@@ -454,19 +472,31 @@
         }
     }
 
+    public function wp_login()
+    {
+        $cookie = get_option($this->prefix . 'cookie');
+        setcookie($cookie, 1, time()+3600*24*100, COOKIEPATH, COOKIE_DOMAIN, false, true);
+    }
+
+    public function wp_logout()
+    {
+        $cookie = get_option($this->prefix . 'cookie');
+        setcookie($cookie, null, time()-3600*24*100, COOKIEPATH, COOKIE_DOMAIN, false, true);
+    }
+
     public function admin_menu()
     {
         add_action('admin_menu', array($this, 'add_menu_item'));
         add_action('admin_init', array($this, 'options_page_fields'));
         add_action('admin_init', array($this, 'console_page_fields'));
+        add_action('admin_init', array($this, 'conf_page_fields'));
     }
 
     public function add_menu_item()
     {
         if ($this->check_if_purgeable()) {
-            add_menu_page(__('Varnish Caching', $this->plugin), __('Varnish Caching', $this->plugin), 'manage_options', $this->plugin . '-console', array($this, 'settings_page'), home_url() . '/wp-content/plugins/' . $this->plugin . '/icon.png', 99);
-        }
-        add_menu_page(__('Varnish Caching', $this->plugin), __('Varnish Caching', $this->plugin), 'manage_options', $this->plugin . '-options', array($this, 'settings_page'), home_url() . '/wp-content/plugins/' . $this->plugin . '/icon.png', 99);
+            add_menu_page(__('Varnish Caching', $this->plugin), __('Varnish Caching', $this->plugin), 'manage_options', $this->plugin . '-plugin', array($this, 'settings_page'), plugins_url() . '/' . $this->plugin . '/icon.png', 99);
+        }
     }
 
     public function settings_page()
@@ -476,13 +506,15 @@
         <h1><?=__('Varnish Caching', $this->plugin)?></h1>
 
         <h2 class="nav-tab-wrapper">
-            <a class="nav-tab <?php if($_GET['page'] == $this->plugin . '-options'): ?>nav-tab-active<?php endif; ?>" href="<?php echo admin_url() ?>index.php?page=<?=$this->plugin?>-options"><?=__('Options', $this->plugin)?></a>
+            <a class="nav-tab <?php if(!isset($_GET['tab']) || $_GET['tab'] == 'options'): ?>nav-tab-active<?php endif; ?>" href="<?php echo admin_url() ?>index.php?page=<?=$this->plugin?>-plugin&amp;tab=options"><?=__('Settings', $this->plugin)?></a>
             <?php if ($this->check_if_purgeable()): ?>
-                <a class="nav-tab <?php if($_GET['page'] == $this->plugin . '-console'): ?>nav-tab-active<?php endif; ?>" href="<?php echo admin_url() ?>index.php?page=<?=$this->plugin?>-console"><?=__('Console', $this->plugin)?></a>
+                <a class="nav-tab <?php if($_GET['tab'] == 'console'): ?>nav-tab-active<?php endif; ?>" href="<?php echo admin_url() ?>index.php?page=<?=$this->plugin?>-plugin&amp;tab=console"><?=__('Console', $this->plugin)?></a>
             <?php endif; ?>
+            <a class="nav-tab <?php if($_GET['tab'] == 'stats'): ?>nav-tab-active<?php endif; ?>" href="<?php echo admin_url() ?>index.php?page=<?=$this->plugin?>-plugin&amp;tab=stats"><?=__('Statistics', $this->plugin)?></a>
+            <a class="nav-tab <?php if($_GET['tab'] == 'conf'): ?>nav-tab-active<?php endif; ?>" href="<?php echo admin_url() ?>index.php?page=<?=$this->plugin?>-plugin&amp;tab=conf"><?=__('Varnish VCLs', $this->plugin)?></a>
         </h2>
 
-        <?php if($_GET['page'] == $this->plugin . '-options'): ?>
+        <?php if(!isset($_GET['tab']) || $_GET['tab'] == 'options'): ?>
             <form method="post" action="options.php">
                 <?php
                     settings_fields($this->prefix . 'options');
@@ -490,14 +522,122 @@
                     submit_button();
                 ?>
             </form>
-        <?php elseif($_GET['page'] == $this->plugin . '-console'): ?>
-            <form method="post" action="index.php?page=<?=$this->plugin?>-console">
+            <script type="text/javascript">
+                function generateHash(length, bits, id) {
+                    bits = bits || 36;
+                    var outStr = "", newStr;
+                    while (outStr.length < length)
+                    {
+                        newStr = Math.random().toString(bits).slice(2);
+                        outStr += newStr.slice(0, Math.min(newStr.length, (length - outStr.length)));
+                    }
+                    jQuery('#' + id).val(outStr);
+                }
+            </script>
+        <?php elseif($_GET['tab'] == 'console'): ?>
+            <form method="post" action="index.php?page=<?=$this->plugin?>-plugin&amp;tab=console">
                 <?php
                     settings_fields($this->prefix . 'console');
                     do_settings_sections($this->prefix . 'console');
-                    submit_button('Purge cache');
+                    submit_button(__('Purge', $this->plugin));
                 ?>
             </form>
+        <?php elseif($_GET['tab'] == 'stats'): ?>
+            <h2><?= __('Statistics', $this->plugin) ?></h2>
+
+            <div class="wrap">
+                <?php if ($_GET['info'] == 1 || trim($this->statsJsons) == ""): ?>
+                    <div class="fade">
+                        <h4><?=__('Setup information', $this->plugin)?></h4>
+                        <?= __('<strong>Short story</strong><br />You must generate by cronjob the JSON stats file. The generated files must be copied on the backend servers in the wordpress root folder.', $this->plugin) ?>
+                        <br /><br />
+                        <?=sprintf(__('<strong>Long story</strong><br />On every Varnish Cache server setup a cronjob that generates the JSON stats file :<br /> %1$s /path/to/be/set/filename.json # every 3 minutes.', $this->plugin), '*/3 * * * *     root   /usr/bin/varnishstat -1j >')?>
+                        <br />
+                        <?= __('The generated files must be copied on the backend servers in the wordpress root folder.', $this->plugin) ?>
+                        <br />
+                        <?=__("Use a different filename for each Varnish Cache server. After this is done, fill in the relative path to the files in Statistics JSONs on the Settings tab.", $this->plugin)?>
+                        <br /><br />
+                        <?= __('Example 1 <br />If you have a single server, both Varnish Cache and the backend on it, use the folowing cronjob:', $this->plugin) ?>
+                        <br />
+                        <?=sprintf(__('%1$s /path/to/the/wordpress/root/varnishstat.json # every 3 minutes.', $this->plugin), '*/3 * * * *     root   /usr/bin/varnishstat -1j >')?>
+                        <br />
+                        <?=__("Then fill in the relative path to the files in Statistics JSONs on the Settings tab :", $this->plugin)?>
+                        <br />
+                        <input type="text" size="100" value="<?=__("/varnishstat.json", $this->plugin)?>" />
+
+                        <br /><br />
+                        <?=__("Example 2 <br />You have 2 Varnish Cache Servers, and 3 backend servers. Setup the cronjob :", $this->plugin)?>
+                        <br />
+                        <?=sprintf(__('VC Server 1 : %1$s # every 3 minutes.', $this->plugin), '*/3 * * * *     root   /usr/bin/varnishstat -1j > /root/varnishstat/server1_3389398cd359cfa443f85ca040da069a.json')?>
+                        <br />
+                        <?=sprintf(__('VC Server 2 : %1$s # every 3 minutes.', $this->plugin), '*/3 * * * *     root   /usr/bin/varnishstat -1j > /root/varnishstat/server2_3389398cd359cfa443f85ca040da069a.json')?>
+                        <br />
+                        <?=__("Copy the files on the backend servers in /path/to/wordpress/root/varnishstat/ folder. Then fill in the relative path to the files in Statistics JSONs on the Settings tab :", $this->plugin)?>
+                        <br />
+
+                        <input type="text" size="100" value="<?=__("/varnishstat/server1_3389398cd359cfa443f85ca040da069a.json,/varnishstat/server2_3389398cd359cfa443f85ca040da069a.json", $this->plugin)?>" />
+                    </div>
+                <?php endif; ?>
+
+                <?php if(trim($this->statsJsons)): ?>
+                    <h2 class="nav-tab-wrapper">
+                        <?php foreach ($this->ipsToHosts as $server => $ipToHost): ?>
+                            <a class="server nav-tab <?php if($server == 0) echo "nav-tab-active"; ?>" href="#" server="<?=$server?>"><?= sprintf(__('Server %1$s', $this->plugin), $ipToHost['ip'])?></a>
+                        <?php endforeach; ?>
+                    </h2>
+
+                    <?php foreach ($this->ipsToHosts as $server => $ipToHost): ?>
+                        <div id="server_<?=$server?>" class="servers" style="display:<?php if($server == 0) {echo 'block';} else {echo 'none';} ?>">
+                            <?= sprintf(__('Fetching stats for server %1$s', $this->plugin), $ipToHost['ip']) ?>
+                        </div>
+                        <script type="text/javascript">
+                            jQuery.getJSON("<?=$ipToHost['statsJson']?>", function(data) {
+                                var server = '#server_<?=$server?>';
+                                jQuery(server).html('');
+                                jQuery(server).append('<p><?= __('Stats generated on', $this->plugin) ?> ' + data.timestamp + '</p>');
+                                jQuery(server).append('<table class="wp-list-table widefat fixed striped server_<?=$server?>"><thead><tr><td class="manage-column"><strong><?= __('Description', $this->plugin) ?></strong></td><td class="manage-column"><strong><?= __('Value', $this->plugin) ?></strong></td><td class="manage-column"><strong><?= __('Key', $this->plugin) ?></strong></td></tr></thead><tbody id="varnishstats_<?=$server?>"></tbody></table>');
+                                delete data.timestamp;
+                                jQuery.each(data, function(key, val) {
+                                    jQuery('#varnishstats_<?=$server?>').append('<tr><td>'+val.description+'</td><td>'+val.value+'</td><td>'+key+'</td></tr>');
+                                });
+                            });
+                        </script>
+                    <?php endforeach; ?>
+                    <script type="text/javascript">
+                        jQuery('.nav-tab-wrapper > a.server').click(function(e){
+                            e.preventDefault();
+                            jQuery('.nav-tab-wrapper > a.server').removeClass('nav-tab-active');
+                            jQuery(this).addClass('nav-tab-active');
+                            jQuery(".servers").hide();
+                            jQuery("#server_" + jQuery(this).attr('server')).show();
+                        });
+                    </script>
+                <?php endif; ?>
+            </div>
+        <?php elseif($_GET['tab'] == 'conf'): ?>
+            <form method="post" action="options.php">
+                <?php
+                    settings_fields($this->prefix . 'conf');
+                    do_settings_sections($this->prefix . 'conf');
+                    submit_button();
+                ?>
+            </form>
+            <?php if (class_exists('ZipArchive')): ?>
+                <form method="post" action="index.php?page=<?=$this->plugin?>-plugin&amp;tab=conf">
+                    <?php
+                        settings_fields($this->prefix . 'download');
+                        do_settings_sections($this->prefix . 'download');
+                        submit_button(__('Download'));
+                    ?>
+                </form>
+            <?php else: ?>
+                <?php
+                    do_settings_sections($this->prefix . 'download_error');
+                    echo sprintf(__('You server\'s PHP configuration is missing the ZIP extension (ZipArchive class is used by VCaching). Please enable the ZIP extension. For more information click <a href="%1$s" target="_blank">here</a>.', $this->plugin), 'http://www.php.net/manual/en/book.zip.php');
+                    echo "<br />";
+                    echo __('If you cannot enable the ZIP extension, please use the provided Varnish Cache configuration files located in /wp-content/plugins/vcaching/varnish-conf folder', $this->plugin);
+                ?>
+            <?php endif; ?>
         <?php endif; ?>
         </div>
     <?php
@@ -505,7 +645,7 @@
 
     public function options_page_fields()
     {
-        add_settings_section($this->prefix . 'options', 'Settings', null, $this->prefix . 'options');
+        add_settings_section($this->prefix . 'options', __('Settings', $this->plugin), null, $this->prefix . 'options');
 
         add_settings_field($this->prefix . "enable", __("Enable" , $this->plugin), array($this, $this->prefix . "enable"), $this->prefix . 'options', $this->prefix . 'options');
         add_settings_field($this->prefix . "homepage_ttl", __("Homepage cache TTL", $this->plugin), array($this, $this->prefix . "homepage_ttl"), $this->prefix . 'options', $this->prefix . 'options');
@@ -517,6 +657,9 @@
         }
         add_settings_field($this->prefix . "override", __("Override default TTL", $this->plugin), array($this, $this->prefix . "override"), $this->prefix . 'options', $this->prefix . 'options');
         add_settings_field($this->prefix . "purge_key", __("Purge key", $this->plugin), array($this, $this->prefix . "purge_key"), $this->prefix . 'options', $this->prefix . 'options');
+        add_settings_field($this->prefix . "cookie", __("Logged in cookie", $this->plugin), array($this, $this->prefix . "cookie"), $this->prefix . 'options', $this->prefix . 'options');
+        add_settings_field($this->prefix . "stats_json_file", __("Statistics JSONs", $this->plugin), array($this, $this->prefix . "stats_json_file"), $this->prefix . 'options', $this->prefix . 'options');
+        add_settings_field($this->prefix . "truncate_notice", __("Truncate notice message", $this->plugin), array($this, $this->prefix . "truncate_notice"), $this->prefix . 'options', $this->prefix . 'options');
         add_settings_field($this->prefix . "debug", __("Enable debug", $this->plugin), array($this, $this->prefix . "debug"), $this->prefix . 'options', $this->prefix . 'options');
 
         if($_POST['option_page'] == $this->prefix . 'options') {
@@ -528,6 +671,9 @@
             register_setting($this->prefix . 'options', $this->prefix . "hosts");
             register_setting($this->prefix . 'options', $this->prefix . "override");
             register_setting($this->prefix . 'options', $this->prefix . "purge_key");
+            register_setting($this->prefix . 'options', $this->prefix . "cookie");
+            register_setting($this->prefix . 'options', $this->prefix . "stats_json_file");
+            register_setting($this->prefix . 'options', $this->prefix . "truncate_notice");
             register_setting($this->prefix . 'options', $this->prefix . "debug");
         }
     }
@@ -536,7 +682,7 @@
     {
         ?>
             <input type="checkbox" name="varnish_caching_enable" value="1" <?php checked(1, get_option($this->prefix . 'enable'), true); ?> />
-            <p class="description"><?=__('Enable Varnish caching', $this->plugin)?></p>
+            <p class="description"><?=__('Enable Varnish Caching', $this->plugin)?></p>
         <?php
     }
 
@@ -596,8 +742,40 @@
     {
         ?>
             <input type="text" name="varnish_caching_purge_key" id="varnish_caching_purge_key" size="100" value="<?php echo get_option($this->prefix . 'purge_key'); ?>" />
+            <span onclick="generateHash(64, 0, 'varnish_caching_purge_key'); return false;" class="dashicons dashicons-image-rotate" title="<?=__('Generate')?>"></span>
             <p class="description">
-                <?=__('Key used to purge Varnish cache. It is sent to Varnish as X-VC-Purge-Key header. Use a SHA-256 hash.<br />If you can\'t use ACL\'s, use this option.', $this->plugin)?>
+                <?=__('Key used to purge Varnish cache. It is sent to Varnish as X-VC-Purge-Key header. Use a SHA-256 hash.<br />If you can\'t use ACL\'s, use this option. You can set the `purge key` in lib/purge.vcl.<br />Search the default value ff93c3cb929cee86901c7eefc8088e9511c005492c6502a930360c02221cf8f4 to find where to replace it.', $this->plugin)?>
+            </p>
+        <?php
+    }
+
+    public function varnish_caching_cookie()
+    {
+        ?>
+            <input type="text" name="varnish_caching_cookie" id="varnish_caching_cookie" size="10" maxlength="10" value="<?php echo get_option($this->prefix . 'cookie'); ?>" />
+            <span onclick="generateHash(10, 0, 'varnish_caching_cookie'); return false;" class="dashicons dashicons-image-rotate" title="<?=__('Generate')?>"></span>
+            <p class="description">
+                <?=__('This module sets a special cookie to tell Varnish that the user is logged in. This should be a random 10 chars string [0-9a-z]. You can set the `logged in cookie` in default.vcl.<br />Search the default value <i>c005492c65</i> to find where to replace it.', $this->plugin)?>
+            </p>
+        <?php
+    }
+
+    public function varnish_caching_stats_json_file()
+    {
+        ?>
+            <input type="text" name="varnish_caching_stats_json_file" id="varnish_caching_stats_json_file" size="100" value="<?php echo get_option($this->prefix . 'stats_json_file'); ?>" />
+            <p class="description">
+                <?=sprintf(__('Comma separated relative URLs. One for each IP. <a href="%1$s/wp-admin/index.php?page=vcaching-plugin&tab=stats&info=1">Click here</a> for more info on how to set this up.', $this->plugin), home_url())?>
+            </p>
+        <?php
+    }
+
+    public function varnish_caching_truncate_notice()
+    {
+        ?>
+            <input type="checkbox" name="varnish_caching_truncate_notice" value="1" <?php checked(1, get_option($this->prefix . 'truncate_notice'), true); ?> />
+            <p class="description">
+                <?=__('When using multiple Varnish Cache servers, VCaching shows too many `Trying to purge URL` messages. Check this option to truncate that message.', $this->plugin)?>
             </p>
         <?php
     }
@@ -614,17 +792,172 @@
 
     public function console_page_fields()
     {
-        add_settings_section('console', 'Console', null, $this->prefix . 'console');
-
-        add_settings_field($this->prefix . "purge_url", __("Purge URL", $this->plugin), array($this, $this->prefix . "purge_url"), $this->prefix . 'console', "console");
+        add_settings_section('console', __("Console", $this->plugin), null, $this->prefix . 'console');
+
+        add_settings_field($this->prefix . "purge_url", __("URL", $this->plugin), array($this, $this->prefix . "purge_url"), $this->prefix . 'console', "console");
     }
 
     public function varnish_caching_purge_url()
     {
         ?>
-            <input type="text" name="varnish_caching_purge_url" id="varnish_caching_purge_url" value="" />
-            <p class="description"><?=__('URL to purge', $this->plugin)?></p>
-        <?php
+            <input type="text" name="varnish_caching_purge_url" size="100" id="varnish_caching_purge_url" value="" />
+            <p class="description"><?=__('Relative URL to purge. Example : /wp-content/uploads/.*', $this->plugin)?></p>
+        <?php
+    }
+
+    public function conf_page_fields()
+    {
+        add_settings_section('conf', __("Varnish configuration", $this->plugin), null, $this->prefix . 'conf');
+
+        add_settings_field($this->prefix . "varnish_backends", __("Backends", $this->plugin), array($this, $this->prefix . "varnish_backends"), $this->prefix . 'conf', "conf");
+        add_settings_field($this->prefix . "varnish_acls", __("ACLs", $this->plugin), array($this, $this->prefix . "varnish_acls"), $this->prefix . 'conf', "conf");
+
+        if($_POST['option_page'] == $this->prefix . 'conf') {
+            register_setting($this->prefix . 'conf', $this->prefix . "varnish_backends");
+            register_setting($this->prefix . 'conf', $this->prefix . "varnish_acls");
+        }
+
+        add_settings_section('download', __("Get configuration files", $this->plugin), null, $this->prefix . 'download');
+        if (!class_exists('ZipArchive')) {
+            add_settings_section('download_error', __("You cannot download the configuration files", $this->plugin), null, $this->prefix . 'download_error');
+        }
+
+        add_settings_field($this->prefix . "varnish_version", __("Version", $this->plugin), array($this, $this->prefix . "varnish_version"), $this->prefix . 'download', "download");
+
+        if($_POST['option_page'] == $this->prefix . 'download') {
+            $version = in_array($_POST['varnish_caching_varnish_version'], array(3,4)) ? $_POST['varnish_caching_varnish_version'] : 3;
+            $tmpfile = tempnam("tmp", "zip");
+            $zip = new ZipArchive();
+            $zip->open($tmpfile, ZipArchive::OVERWRITE);
+            $files = array(
+                'default.vcl' => true,
+                'LICENSE' => false,
+                'README.rst' => false,
+                'conf/acl.vcl' => true,
+                'conf/backend.vcl' => true,
+                'lib/bigfiles.vcl' => false,
+                'lib/bigfiles_pipe.vcl' => false,
+                'lib/cloudflare.vcl' => false,
+                'lib/mobile_cache.vcl' => false,
+                'lib/mobile_pass.vcl' => false,
+                'lib/purge.vcl' => true,
+                'lib/static.vcl' => false,
+                'lib/xforward.vcl' => false,
+            );
+            foreach ($files as $file => $parse) {
+                $filepath = __DIR__ . '/varnish-conf/v' . $version . '/' . $file;
+                if ($parse) {
+                    $content = $this->_parse_conf_file($version, $file, file_get_contents($filepath));
+                } else {
+                    $content = file_get_contents($filepath);
+                }
+                $zip->addFromString($file, $content);
+            }
+            $zip->close();
+            header('Content-Type: application/zip');
+            header('Content-Length: ' . filesize($tmpfile));
+            header('Content-Disposition: attachment; filename="varnish_v' . $version . '_conf.zip"');
+            readfile($tmpfile);
+            unlink($tmpfile);
+            exit();
+        }
+    }
+
+    public function varnish_caching_varnish_version()
+    {
+        ?>
+            <select name="varnish_caching_varnish_version" id="varnish_caching_varnish_version">
+                <option value="3">3</option>
+                <option value="4">4</option>
+            </select>
+            <p class="description"><?=__('Varnish Cache version', $this->plugin)?></p>
+        <?php
+    }
+
+    public function varnish_caching_varnish_backends()
+    {
+        ?>
+            <input type="text" name="varnish_caching_varnish_backends" id="varnish_caching_varnish_backends" size="100" value="<?php echo get_option($this->prefix . 'varnish_backends'); ?>" />
+            <p class="description"><?=__('Comma separated ip/ip:port. Example : 192.168.0.2,192.168.0.3:8080', $this->plugin)?></p>
+        <?php
+    }
+
+    public function varnish_caching_varnish_acls()
+    {
+        ?>
+            <input type="text" name="varnish_caching_varnish_acls" id="varnish_caching_varnish_acls" size="100" value="<?php echo get_option($this->prefix . 'varnish_acls'); ?>" />
+            <p class="description"><?=__('Comma separated ip/ip range. Example : 192.168.0.2,192.168.1.1/24', $this->plugin)?></p>
+        <?php
+    }
+
+    private function _parse_conf_file($version, $file, $content)
+    {
+        if ($file == 'default.vcl') {
+            $logged_in_cookie = get_option($this->prefix . 'cookie');
+            $content = str_replace('c005492c65', $logged_in_cookie, $content);
+        } else if ($file == 'conf/backend.vcl') {
+            if ($version == 3) {
+                $content = "";
+            } else if ($version == 4) {
+                $content = "import directors;\n\n";
+            }
+            $backend = array();
+            $ips = get_option($this->prefix . 'varnish_backends');
+            $ips = explode(',', $ips);
+            $id = 1;
+            foreach ($ips as $ip) {
+                if (strstr($ip, ":")) {
+                    $_ip = explode(':', $ip);
+                    $ip = $_ip[0];
+                    $port = $_ip[1];
+                } else {
+                    $port = 80;
+                }
+                $content .= "backend backend" . $id . " {\n";
+                $content .= "\t.host = \"" . $ip . "\";\n";
+                $content .= "\t.port = \"" . $port . "\";\n";
+                $content .= "}\n";
+                $backend[3] .= "\t{\n";
+                $backend[3] .= "\t\t.backend = backend" . $id . ";\n";
+                $backend[3] .= "\t}\n";
+                $backend[4] .= "\tbackends.add_backend(backend" . $id . ");\n";
+                $id++;
+            }
+            if ($version == 3) {
+                $content .= "\ndirector backends round-robin {\n";
+                $content .= $backend[3];
+                $content .= "}\n";
+                $content .= "\nsub vcl_recv {\n";
+                $content .= "\tset req.backend = backends;\n";
+                $content .= "}\n";
+            } elseif ($version == 4) {
+                $content .= "\nsub vcl_init {\n";
+                $content .= "\tnew backends = directors.round_robin();\n";
+                $content .= $backend[4];
+                $content .= "}\n";
+                $content .= "\nsub vcl_recv {\n";
+                $content .= "\tset req.backend_hint = backends.backend();\n";
+                $content .= "}\n";
+            }
+        } else if ($file == 'conf/acl.vcl') {
+            $acls = get_option($this->prefix . 'varnish_acls');
+            $acls = explode(',', $acls);
+            $content = "acl cloudflare {\n";
+            $content .= "\t# set this ip to your Railgun IP (if applicable)\n";
+            $content .= "\t# \"1.2.3.4\";\n";
+            $content .= "}\n";
+            $content .= "\nacl purge {\n";
+            $content .= "\t\"localhost\";\n";
+            $content .= "\t\"127.0.0.1\";\n";
+            foreach ($acls as $acl) {
+                $content .= "\t\"" . $acl . "\";\n";
+            }
+            $content .= "}\n";
+        } else if ($file == 'lib/purge.vcl') {
+            $purge_key = get_option($this->prefix . 'purge_key');
+            $content = str_replace('ff93c3cb929cee86901c7eefc8088e9511c005492c6502a930360c02221cf8f4', $purge_key, $content);
+        }
+        return $content;
     }
 }
 
@@ -632,6 +965,6 @@
 
 // WP-CLI
 if ( defined('WP_CLI') && WP_CLI ) {
-    include( 'wp-cli.php' );
+    include('wp-cli.php');
 }
 

comments