From tfheen at varnish-software.com Mon Dec 2 13:12:35 2013 From: tfheen at varnish-software.com (Tollef Fog Heen) Date: Mon, 2 Dec 2013 14:12:35 +0100 Subject: Varnish Cache 3.0.5 released Message-ID: <20131202131235.GA27596@err.no> It is my pleasure to announce the release of Varnish Cache 3.0.5. This is a bugfix release which fixes amongst other errors CVE-2013-4484 where a malformed request and a particular configuration could cause Varnish to crash. Some other changes include: * Fix bad interaction between -m, -c and -b for varnishlog. * Prevent duplicate Content-Length headers being sent to clients when streaming is enabled. * Stop printing ESI parse errors to stdout. * Stop segfaulting if the first part of a synthetic page is NULL. A fuller list of changes is available from http://varnish-cache.org/trac/browser/doc/changes.rst Installation instructions and sources are available from https://www.varnish-cache.org/releases/varnish-cache-3.0.5 -- Tollef Fog Heen, on behalf of the Varnish team From tfheen at varnish-software.com Thu Dec 5 08:08:56 2013 From: tfheen at varnish-software.com (Tollef Fog Heen) Date: Thu, 5 Dec 2013 09:08:56 +0100 Subject: Varnish 4.0.0 technology preview 1 released Message-ID: <20131205080856.GA15656@err.no> Hot on the heels of Varnish 3.0.5, it is my pleasure to announce the release of Varnish 4.0.0 technology preview 1.? There are too many changes to fully enumerate them here, but a small sample is: ?- Full streaming support, including asynchronous backend fetches. ?? This enables Varnish to serve stale objects while it is fetching or ?? revalidating objects from the backend. ?- If-Modified-Since and If-None-Match support to the backend. ?- Directors are now VMODs and are runtime loadable. ?- A complete overhaul of the libvarnishapi and corresponding tools, ?? leading to performance and correctness improvements. ?- A more fully-fledged filtering language for querying the Varnish ?? logs. Please note the VCL syntax has changed and requires upgrading from previous versions. Known issues and limitations: ???? ?- varnishhist and varnishtop are known to not work correctly. ? ?- the documentation is not properly updated yet.? In particular, there is not yet any upgrade checklist. You can download the new release from http://repo.varnish-cache.org/source/varnish-4.0.0-tp1.tar.gz or replace varnish-3.0 with varnish-4.0 in the regular installation instructions. As this release is a technology preview, it is not recommended for production systems.? Feedback on varnish-dev at varnish-cache.org and #varnish-hacking on irc.linpro.no is most? welcome. -- Tollef Fog Heen, on behalf of the Varnish team From phk at phk.freebsd.dk Thu Dec 5 10:33:54 2013 From: phk at phk.freebsd.dk (Poul-Henning Kamp) Date: Thu, 05 Dec 2013 10:33:54 +0000 Subject: The Happy-Happy Sort-of-Varnish-4.0 2013 Status Email Message-ID: <25549.1386239634@critter.freebsd.dk> This is the annual Varnish Project status email, and as usual I'll try to keep it short: VUG8 ---- We just came home from a great VUG8 in Berlin. Many thanks to the sponsors, Fastly, Axel Springer, UPLEX & Varnish Software for making this possible. Ruben has updated the VUG8 page with links to videos og slides: https://www.varnish-cache.org/vug8 Find a moment to watch Martins and my talks about what's new in Varnish V4. The list is too long to repeat here, but the two absolute highlights are: 1. Truly asynchronous backend fetches with full streaming. 2. New varnishlog filter-language (Martin did this!) If you want to sponsor VUG9 or to make VUG9 come to your city, talk to Ruben about it. (He is also planning Varnish-4 release parties, once the 4.0-RELEASE comes out, he will send mail about that later.) 4.0-TP1 ------- A few hours ago Tollef released "Varnish 4.0-Tech-Preview-1" As the name should make obvious, we don't expect you to rush this new version into production over the holidays, at least not these holidays, but we hope you will take some time to play with it. The point about this release is to get the new code out there for you to test and experiment with, because there are a LOT of good new stuff, and undoubtedly also some new bugs, and we'd like to get those found and fixed before we call it 4.0-Release. The "real" 4.0-RELEASE will happen once our QA and documentation efforts are completed, and the more you guys help us test and stress the new code, the sooner that can happen. Have at it, and if you find bugs, please open a ticket about it so we can fix it. Varnish Moral License --------------------- I earn my living from my one-man company, and the work I do on Varnish is paid for by companies which pay for a Varnish Moral Licenses. This year i have been able to spend approx 900 hours on developing Varnish this year thanks to (in alphabetically sorted, 3rd letter): Radio New Zealand, UPLEX, DYN, GLOBO.com, Varnish Software Thanks a LOT for that. But... The last couple of months I have been burning through VML money at about twice the rate it has come in. This means that we get a lot of stuff done, but it also means that the VML silo is rapidly running out of money. Obviously I must either sell more Varnish Moral Licenses to keep going at this rate, or scale back my Varnish work and find some contracts to fill my time. I'd much prefer the former. If your company makes money running Varnish, please consider pitching in: Investing in Varnish development is how you make sure that Varnish will work great for your website in the future. You can read all about the VML here: http://phk.freebsd.dk/VML/ And since this invariably causes some emails along the lines of "I wish, but..." I will mention that you can also show your appreciation by spelunking my Amazon wish list: http://www.amazon.com/exec/obidos/wishlist/1XSZNDWXKIAS0 Thanks in advance, Poul-Henning Kamp -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk at FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence.