In all my previous Varnish 3.x configs, I’ve always used blacklisting as the way of handling Cookies. You explicitly tell which cookies you want to remove in vcl_recv, all others remain. But just as security measures, whitelisting is always better than blacklisting.
Here’s what happend last week on this blog, just in case you missed it. The Real Cost of the “S” in HTTPS The Pirate Bay calls it quits Generate PHP core dumps on segfaults in PHP-FPM Varnish tip: see which cookies are being stripped in your VCL Chrome To Explicitly Mark HTTP Connections As Non-Secure […]
You can reload the Varnish VCL configuration without actually restarting Varnish. A restart would stop the varnishd process and start it anew, clearing all the cache it has built up in the meantime. But you can also reload the varnish configurations, to load your new VCL without losing the cache. Beware though, there are times […]
Good news! Today, Varnish 4.0.0 has been released!. Among the most important features are; * Full support for streaming objects through from the backend on a cache miss. Bytes will be sent to 1..n requesting clients as they come in from the backend server. * Background (re)fetch of expired objects. On a cache miss where […]