r2305 - in branches/1.1: . doc

des at projects.linpro.no des at projects.linpro.no
Tue Dec 18 18:05:06 CET 2007


Author: des
Date: 2007-12-18 18:05:05 +0100 (Tue, 18 Dec 2007)
New Revision: 2305

Added:
   branches/1.1/doc/changes-1.1.1-1.1.2.xml
   branches/1.1/doc/changes-1.1.2.xml
Modified:
   branches/1.1/
   branches/1.1/doc/Makefile.am
Log:
Merged revisions 2207,2216-2219,2221,2233-2242,2244-2245,2256-2262,2296-2297,2299-2301 via svnmerge from 
svn+ssh://projects.linpro.no/svn/varnish/trunk/varnish-cache

........
  r2207 | des | 2007-10-30 13:36:09 +0100 (Tue, 30 Oct 2007) | 2 lines
  
  Incomplete change log for 1.1.2
........
  r2300 | des | 2007-12-18 18:00:19 +0100 (Tue, 18 Dec 2007) | 4 lines
  
  Full change log for 1.1.2 (corresponding to branches/1.1 as of today).
  References to tickets have been included where I have been able to track
  down the ticket corresponding to a particular commit.
........
  r2301 | des | 2007-12-18 18:00:29 +0100 (Tue, 18 Dec 2007) | 2 lines
  
  Build the 1.1.2 change log.
........



Property changes on: branches/1.1
___________________________________________________________________
Name: svnmerge-integrated
   - /trunk/varnish-cache:1-1722,1727-1729,1733,1738,1743-1777,1779-1798,1800-1815,1817,1819,1823,1830-1838,1846,1853-1855,1857-1859,1862,1865-1868,1871-1880,1883-1884,1886,1888-1889,1896,1898,1902-1905,1907,1909,1912-1916,1920-1928,1935-1939,1941-1949,1955,1957-1958,1967-1968,1970-1974,1976-1977,1984,1986-1989,1991-1998,2026,2031-2033,2057,2077-2080,2086,2088,2097,2106-2107,2116,2133,2154,2173,2181,2206,2211-2212,2215-2220,2222-2232,2243,2270-2271,2275,2298
   + /trunk/varnish-cache:1-1722,1727-1729,1733,1738,1743-1777,1779-1798,1800-1815,1817,1819,1823,1830-1838,1846,1853-1855,1857-1859,1862,1865-1868,1871-1880,1883-1884,1886,1888-1889,1896,1898,1902-1905,1907,1909,1912-1916,1920-1928,1935-1939,1941-1949,1955,1957-1958,1967-1968,1970-1974,1976-1977,1984,1986-1989,1991-1998,2026,2031-2033,2057,2077-2080,2086,2088,2097,2106-2107,2116,2133,2154,2173,2181,2206-2207,2211-2212,2215-2245,2256-2262,2270-2271,2275,2296-2301

Modified: branches/1.1/doc/Makefile.am
===================================================================
--- branches/1.1/doc/Makefile.am	2007-12-18 17:04:37 UTC (rev 2304)
+++ branches/1.1/doc/Makefile.am	2007-12-18 17:05:05 UTC (rev 2305)
@@ -1,11 +1,13 @@
 # $Id$
 
 CHANGELOGS = \
+	changes-1.1.2.html \
 	changes-1.1.1.html \
 	changes-1.1.html \
 	changes-1.0.4.html
 
 XML = \
+	changes-1.1.1-1.1.2.xml \
 	changes-1.1-1.1.1.xml \
 	changes-1.0.4-1.1.xml \
 	changes-1.0.3-1.0.4.xml \

Copied: branches/1.1/doc/changes-1.1.1-1.1.2.xml (from rev 2207, trunk/varnish-cache/doc/changes-1.1.1-1.1.2.xml)
===================================================================
--- branches/1.1/doc/changes-1.1.1-1.1.2.xml	                        (rev 0)
+++ branches/1.1/doc/changes-1.1.1-1.1.2.xml	2007-12-18 17:05:05 UTC (rev 2305)
@@ -0,0 +1,149 @@
+<?xml version="1.0" encoding="utf-8"?>
+<!DOCTYPE group [
+<!ENTITY mdash "&#8212;">
+]>
+<!-- $Id$ -->
+<group from="1.1.1" to="1.1.2">
+  <subsystem>
+    <name>varnishd</name>
+
+    <change type="bug" ref="1809,1913">
+      <para>When switching to a new VCL configuration, a race
+      condition exists which may cause Varnish to reference a backend
+      which no longer exists (see <ticket ref="144"/>).  This race
+      condition has not been entirely eliminated, but it should occur
+      less frequently.</para>
+    </change>
+
+    <change type="bug" ref="1942">
+      <para>When dropping a TCP session before any requests were
+      processed, an assertion would be triggered due to an
+      uninitialized timestamp (see <ticket ref="132"/>).  The
+      timestamp is now correctly initialized.</para>
+    </change>
+
+    <change type="bug" ref="1955,1976,1977">
+      <para>Varnish will now correctly generate a <code>Date:</code>
+      header for every response instead of copying the one it got from
+      the backend (see <ticket ref="157"/>).</para>
+    </change>
+
+    <change type="bug" ref="1971">
+      <para>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.</para>
+    </change>
+
+    <change type="bug" ref="1972">
+      <para>A bug in the VCL compiler which would cause a double-free
+      when processing <code>include</code> directives has been
+      fixed.</para>
+    </change>
+
+    <change type="bug" ref="1991">
+      <para>A resource leak in the worker thread management code has
+      been fixed.</para>
+    </change>
+
+    <change type="bug" ref="1809">
+      <para>When connecting to a backend, Varnish will usually get the
+      address from a cache.  When the cache is refreshed, existing
+      connections may end up with a reference to an address structure
+      which no longer exists, resulting in a crash.  This race
+      condition has been somewhat mitigated, but not entirely
+      eliminated (see <ticket ref="144"/>.)</para>
+    </change>
+
+    <change type="bug" ref="1888">
+      <para>Varnish will now pass the correct protocol version in pipe
+      mode: the backend will get what the client sent, and vice
+      versa.</para>
+    </change>
+
+    <change type="bug" ref="2057,2077,2080,2086">
+      <para>The core of the pipe mode code has been rewritten to
+      increase robustness and eliminate spurious error messages when
+      either end closes the connection in a manner Varnish did not
+      anticipate.</para>
+    </change>
+
+    <change type="bug" ref="2181">
+      <para>A memory leak in the backend code has been plugged.</para>
+    </change>
+
+    <change type="bug" ref="2232">
+      <para>When using the <code>kqueue</code> acceptor, if a client
+      shuts down the request side of the connection (as many clients
+      do after sending their final request), it was possible for the
+      acceptor code to receive the <code>EOF</code> event and recycle
+      the session while the last request was still being serviced,
+      resulting in a assertion failure and a crash when the worker
+      thread later tried to delete the session.  This should no longer
+      happen (see <ticket ref="162"/>.)</para>
+    </change>
+
+    <change type="bug" ref="2275">
+      <para>A mismatch between the recorded length of a cached object
+      and the amount of data actually present in cache for that object
+      can occasionally occur (see <ticket ref="167"/>.)  This has been
+      partially fixed, but may still occur for error pages generated
+      by Varnish when a problem arises while retrieving an object from
+      the backend.</para>
+    </change>
+  </subsystem>
+
+  <subsystem>
+    <name>varnishhist</name>
+
+    <change type="enh">
+      <para>Pressing <code>0</code> though <code>9</code> while
+      <code>varnishhist</code> is running will change the refresh
+      interval to the corresponding power of two, in seconds.</para>
+    </change>
+  </subsystem>
+
+  <subsystem>
+    <name>varnishncsa</name>
+
+    <change type="enh">
+      <para>The <code>varnishncsa</code> tool can now daemonize and
+      write a PID file like <code>varnishlog</code>, using the same
+      command-line options.  It will also reopen its output upon receipt
+      of a <code>SIGHUP</code> if invoked with <code>-w</code>.</para>
+    </change>
+  </subsystem>
+
+  <subsystem>
+    <name>varnishstat</name>
+
+    <change type="enh">
+      <para>Pressing <code>0</code> though <code>9</code> while
+      <code>varnishstat</code> is running will change the refresh
+      interval to the corresponding power of two, in seconds.</para>
+    </change>
+  </subsystem>
+
+  <subsystem>
+    <name>Build system</name>
+
+    <change type="enh" ref="2033">
+      <para>Varnish's <code>&lt;queue.h&gt;</code> has been modified
+      to avoid conflicts with <code>&lt;sys/queue.h&gt;</code> on
+      platforms where the latter is included indirectly through system
+      headers.</para>
+    </change>
+
+    <change type="enh" ref="2032,2133,2097,2106,2222-2228">
+      <para>Several steps have been taken towards Solaris
+      support, but this is not yet complete.</para>
+    </change>
+
+    <change type="bug" ref="2116,2154">
+      <para>When <code>configure</code> was run without an explicit
+      prefix, Varnish's idea of the default state directory would be
+      garbage and a state directory would have to be specified
+      manually with <code>-n</code>.  This has been corrected.</para>
+    </change>
+  </subsystem>
+</group>

Copied: branches/1.1/doc/changes-1.1.2.xml (from rev 2207, trunk/varnish-cache/doc/changes-1.1.2.xml)
===================================================================
--- branches/1.1/doc/changes-1.1.2.xml	                        (rev 0)
+++ branches/1.1/doc/changes-1.1.2.xml	2007-12-18 17:05:05 UTC (rev 2305)
@@ -0,0 +1,12 @@
+<?xml version="1.0" encoding="utf-8"?>
+<?xml-stylesheet type="text/xml" href="changes-html.xsl"?>
+<!DOCTYPE changelog [
+ <!ENTITY mdash "&#8212;">
+]>
+<!-- $Id$ -->
+<changelog xmlns:xi="http://www.w3.org/2001/XInclude">
+  <package>Varnish</package>
+  <version>1.1.2</version>
+
+  <xi:include href="changes-1.1.1-1.1.2.xml"/>
+</changelog>




More information about the varnish-commit mailing list