Commit 13d89850 authored by Dag Erling Smørgrav's avatar Dag Erling Smørgrav

Merged revisions 1902-1905 via svnmerge from

svn+ssh://projects.linpro.no/svn/varnish/trunk/varnish-cache

........
  r1902 | des | 2007-08-20 21:13:37 +0200 (Mon, 20 Aug 2007) | 2 lines
  
  Render <code> elements.
........
  r1903 | des | 2007-08-20 21:16:08 +0200 (Mon, 20 Aug 2007) | 2 lines
  
  Really render <code> elements correctly.
........
  r1904 | des | 2007-08-20 21:17:49 +0200 (Mon, 20 Aug 2007) | 4 lines
  
  At some point along the line, I forgot that these files aren't actually
  DocBook, and that I don't have <filename>, <literal>, <varname> etc. -
  just <code>.
........
  r1905 | des | 2007-08-20 21:20:25 +0200 (Mon, 20 Aug 2007) | 2 lines
  
  Rewrap (no content changes)
........


git-svn-id: http://www.varnish-cache.org/svn/branches/1.1@1906 d4fa192b-c00b-0410-8231-f00ffab90ce4
parent e3ae4724
This diff is collapsed.
......@@ -9,14 +9,14 @@
<change type="bug" ref="1745">
<para>The code required to allow VCL to read
<varname>obj.status</varname>, which had accidentally been left
out, has now been added.</para>
<code>obj.status</code>, which had accidentally been left out,
has now been added.</para>
</change>
<change type="bug" ref="1750">
<para>Varnish will now always include a
<literal>Connection:</literal> header in its reply to the
client, to avoid possible misunderstandings.</para>
<para>Varnish will now always include a <code>Connection:</code>
header in its reply to the client, to avoid possible
misunderstandings.</para>
</change>
<change type="buf" ref="1751">
......@@ -25,18 +25,18 @@
</change>
<change type="enh" ref="1761,1762,1765,1828">
<para>A new VCL function, <function>purge_url</function>,
provides the same functionality as the
<command>url.purge</command> management command.</para>
<para>A new VCL function, <code>purge_url</code>, provides the
same functionality as the <code>url.purge</code> management
command.</para>
</change>
<change type="enh" ref="1780">
<para>Previously, Varnish assumed that the response body should
be sent only if the request method was <literal>GET</literal>.
This was a problem for custom request methods (such as
<literal>PURGE</literal>), so the logic has been changed to
always send the response body except in the specific case of a
<literal>HEAD</literal> request.</para>
be sent only if the request method was <code>GET</code>. This
was a problem for custom request methods (such as
<code>PURGE</code>), so the logic has been changed to always
send the response body except in the specific case of a
<code>HEAD</code> request.</para>
</change>
<change type="bug" ref="1795">
......@@ -46,11 +46,10 @@
<change type="bug" ref="1797">
<para>Due to the way run-time parameters are initialized at
startup, <command>varnishd</command> previously required the
<literal>nobody</literal> user and the
<literal>nogroup</literal> group to exist even if a different
user and group were specified on the command line. This has
been corrected.</para>
startup, <code>varnishd</code> previously required the
<code>nobody</code> user and the <code>nogroup</code> group to
exist even if a different user and group were specified on the
command line. This has been corrected.</para>
</change>
<change type="bug" ref="1800">
......@@ -66,18 +65,17 @@
</change>
<change type="bug" ref="1807">
<para>Before calling <function>vcl_miss</function>, Varnish
assembles a tentative request object for the backend request
which will usually follow. This object would be leaked if
<function>vcl_miss</function> returned anything else than
<command>fetch</command>. This has been corrected.</para>
<para>Before calling <code>vcl_miss</code>, Varnish assembles a
tentative request object for the backend request which will
usually follow. This object would be leaked if
<code>vcl_miss</code> returned anything else than
<code>fetch</code>. This has been corrected.</para>
</change>
<change type="bug" ref="1808">
<para>The code necessary to handle an <command>error</command>
return from <function>vcl_fetch</function> and
<function>vcl_deliver</function> had inadvertantly been left
out. This has been corrected.</para>
<para>The code necessary to handle an <code>error</code> return
from <code>vcl_fetch</code> and <code>vcl_deliver</code> had
inadvertantly been left out. This has been corrected.</para>
</change>
<change type="bug" ref="1810">
......@@ -109,8 +107,7 @@
<change type="bug" ref="1752">
<para>The top-level Makefile will now honor
<varname>$DESTDIR</varname> when creating the state
directory.</para>
<code>$DESTDIR</code> when creating the state directory.</para>
</change>
<change type="enh" ref="1743,1846">
......@@ -124,16 +121,16 @@
</change>
<change type="enh" ref="1811">
<para>The <filename>autogen.sh</filename> script had workarounds
for problems with the GNU autotools on FreeBSD; these are no
longer needed and have been removed.</para>
<para>The <code>autogen.sh</code> script had workarounds for
problems with the GNU autotools on FreeBSD; these are no longer
needed and have been removed.</para>
</change>
<change type="enh" ref="1817">
<para>The <filename>libcompat</filename> library has been
renamed to <filename>libvarnishcompat</filename> and is now
dynamic rather than static. This simplifies the build process
and resolves an issue with the Mac OS X linker.</para>
<para>The <code>libcompat</code> library has been renamed to
<code>libvarnishcompat</code> and is now dynamic rather than
static. This simplifies the build process and resolves an issue
with the Mac OS X linker.</para>
</change>
</subsystem>
</group>
......@@ -72,4 +72,21 @@
<xsl:value-of select="@ref"/>
</a>
</xsl:template>
<xsl:template match="code">
<span>
<xsl:attribute name="class">
<xsl:value-of select="name()"/>
</xsl:attribute>
<xsl:apply-templates/>
</span>
</xsl:template>
<xsl:template match="*" priority="-1">
<xsl:message>Warning: no template for element <xsl:value-of select="name(
)"/></xsl:message>
<xsl:value-of select="concat('&lt;', name(), '&gt;')"/>
<xsl:apply-templates/>
<xsl:value-of select="concat('&lt;/', name(), '&gt;')"/>
</xsl:template>
</xsl:stylesheet>
......@@ -25,3 +25,7 @@ h3 {
font-weight: bold;
color: maroon;
}
.code {
font-family: monospace;
}
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment