A bit off topic, but Varnish seems to have a valid point about using Varnish and SSL.<p><a href="https://www.varnish-cache.org/docs/trunk/phk/ssl.html" rel="nofollow">https://www.varnish-cache.org/docs/trunk/phk/ssl.html</a><p>"There is no other way we can guarantee that secret krypto-bits do not leak anywhere they should not, than by fencing in the code that deals with them in a child process, so the bulk of varnish never gets anywhere near the certificates, not even during a core-dump."<p>I came across this when looking for https support few weeks ago.
Don't forget the Varnish 4.0 Release Party on April 29th - <a href="http://v4party.varnish-cache.org" rel="nofollow">http://v4party.varnish-cache.org</a> #v4rp
Can anyone who actually understands what the upgrade document states do a how to or a straight modification of a popular vcl, so people who don't have as much experience and pretty much just use these default vcl files?<p>Here's one that I and a few of my friends use routinely:<p><a href="https://github.com/ewanleith/Wordpress-Server-Configuration-Files/blob/master/default.vcl" rel="nofollow">https://github.com/ewanleith/Wordpress-Server-Configuration-...</a><p>Like where do I start if I want to use this thing with 4.0?<p>vcl_fetch needs to be renamed, will this work if I just rename it and add vcl version to the top?
I don't know much about caching.<p>Does this work when serving dynamic content? I mean in a situation where your user absolutely need to see an up-to-date version of your data.
"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." is an awesome feature in and of itself. thank you varnish team, this looks like a great release.
Watching that what-is-varnish video, I was surprised that this seems to be a Norwegian company. The narrator had an American (New England?) accent, not a naive/jovial Norwegian accent.