From ee2f384af7dd643f74f5fa4435e3b851391c6800 Mon Sep 17 00:00:00 2001 From: des Date: Tue, 30 Oct 2007 12:36:09 +0000 Subject: [PATCH] Incomplete change log for 1.1.2 git-svn-id: svn+ssh://projects.linpro.no/svn/varnish/trunk@2207 d4fa192b-c00b-0410-8231-f00ffab90ce4 --- varnish-cache/doc/changes-1.1.1-1.1.2.xml | 53 +++++++++++++++++++++++ varnish-cache/doc/changes-1.1.2.xml | 12 +++++ 2 files changed, 65 insertions(+) create mode 100644 varnish-cache/doc/changes-1.1.1-1.1.2.xml create mode 100644 varnish-cache/doc/changes-1.1.2.xml diff --git a/varnish-cache/doc/changes-1.1.1-1.1.2.xml b/varnish-cache/doc/changes-1.1.1-1.1.2.xml new file mode 100644 index 00000000..76e10f51 --- /dev/null +++ b/varnish-cache/doc/changes-1.1.1-1.1.2.xml @@ -0,0 +1,53 @@ + + +]> + + + + varnishd + + + When switching to a new VCL configuration, a race + condition exists which may cause Varnish to reference a backend + which no longer exists (see ). This race + condition has not been entirely eliminated, but it should occur + less frequently. + + + + When dropping a TCP session before any requests were + processed, an assertion would be triggered due to an + uninitialized timestamp (see ). The + timestamp is now correctly initialized. + + + + Varnish will now correctly generate a Date: + header for every response instead of copying the one it got from + the backend (see ). + + + + Comparisons in VCL which involve a non-existent string + (usually a header which is not present in the request or object + being processed) would cause a NULL pointer dereference; now the + comparison will simply fail. + + + + A bug in the VCL compiler which would cause a double-free + when processing include directives has been + fixed. + + + + + + + + + Build system + + + diff --git a/varnish-cache/doc/changes-1.1.2.xml b/varnish-cache/doc/changes-1.1.2.xml new file mode 100644 index 00000000..e6290030 --- /dev/null +++ b/varnish-cache/doc/changes-1.1.2.xml @@ -0,0 +1,12 @@ + + + +]> + + + Varnish + 1.1.2 + + + -- 2.39.5