httpd-cvs mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From humbed...@apache.org
Subject svn commit: r1334008 [1/2] - /httpd/httpd/branches/2.4.x/docs/manual/mod/
Date Fri, 04 May 2012 15:00:01 GMT
Author: humbedooh
Date: Fri May  4 14:59:59 2012
New Revision: 1334008

URL: http://svn.apache.org/viewvc?rev=1334008&view=rev
Log:
Backporting syntax highlighting for core.xml, mod_a*.xml

Modified:
    httpd/httpd/branches/2.4.x/docs/manual/mod/core.xml
    httpd/httpd/branches/2.4.x/docs/manual/mod/mod_access_compat.xml
    httpd/httpd/branches/2.4.x/docs/manual/mod/mod_actions.xml
    httpd/httpd/branches/2.4.x/docs/manual/mod/mod_alias.xml
    httpd/httpd/branches/2.4.x/docs/manual/mod/mod_allowmethods.xml
    httpd/httpd/branches/2.4.x/docs/manual/mod/mod_asis.xml
    httpd/httpd/branches/2.4.x/docs/manual/mod/mod_auth_basic.xml
    httpd/httpd/branches/2.4.x/docs/manual/mod/mod_auth_digest.xml
    httpd/httpd/branches/2.4.x/docs/manual/mod/mod_auth_form.xml
    httpd/httpd/branches/2.4.x/docs/manual/mod/mod_authn_anon.xml
    httpd/httpd/branches/2.4.x/docs/manual/mod/mod_authn_core.xml
    httpd/httpd/branches/2.4.x/docs/manual/mod/mod_authn_dbd.xml
    httpd/httpd/branches/2.4.x/docs/manual/mod/mod_authn_socache.xml
    httpd/httpd/branches/2.4.x/docs/manual/mod/mod_authnz_ldap.xml
    httpd/httpd/branches/2.4.x/docs/manual/mod/mod_authz_core.xml
    httpd/httpd/branches/2.4.x/docs/manual/mod/mod_authz_dbd.xml
    httpd/httpd/branches/2.4.x/docs/manual/mod/mod_authz_dbm.xml
    httpd/httpd/branches/2.4.x/docs/manual/mod/mod_authz_host.xml
    httpd/httpd/branches/2.4.x/docs/manual/mod/mod_authz_owner.xml
    httpd/httpd/branches/2.4.x/docs/manual/mod/mod_autoindex.xml

Modified: httpd/httpd/branches/2.4.x/docs/manual/mod/core.xml
URL: http://svn.apache.org/viewvc/httpd/httpd/branches/2.4.x/docs/manual/mod/core.xml?rev=1334008&r1=1334007&r2=1334008&view=diff
==============================================================================
--- httpd/httpd/branches/2.4.x/docs/manual/mod/core.xml (original)
+++ httpd/httpd/branches/2.4.x/docs/manual/mod/core.xml Fri May  4 14:59:59 2012
@@ -48,7 +48,9 @@ On Windows from Apache httpd 2.3.3 and l
     <p>Using <code>none</code> for an argument will disable any accept filters
        for that protocol.  This is useful for protocols that require a server
        send data first, such as <code>ftp:</code> or <code>nntp</code>:</p>
-    <example>AcceptFilter nntp none</example>
+    <highlight language="config">
+    AcceptFilter nntp none
+    </highlight>
 
     <p>The default protocol names are <code>https</code> for port 443
        and <code>http</code> for all other ports.  To specify another protocol
@@ -57,10 +59,10 @@ On Windows from Apache httpd 2.3.3 and l
        directive.</p>
 
     <p>The default values on FreeBSD are:</p>
-    <example>
-        AcceptFilter http httpready <br/>
-        AcceptFilter https dataready
-    </example>
+    <highlight language="config">
+AcceptFilter http httpready
+AcceptFilter https dataready
+    </highlight>
 
     <p>The <code>httpready</code> accept filter buffers entire HTTP requests at
        the kernel level.  Once an entire request is received, the kernel then
@@ -71,10 +73,10 @@ On Windows from Apache httpd 2.3.3 and l
        accf_data(9)</a> filter is used.</p>
 
     <p>The default values on Linux are:</p>
-    <example>
-        AcceptFilter http data <br/>
-        AcceptFilter https data
-    </example>
+    <highlight language="config">
+AcceptFilter http data
+AcceptFilter https data
+    </highlight>
 
     <p>Linux's <code>TCP_DEFER_ACCEPT</code> does not support buffering http
        requests.  Any value besides <code>none</code> will enable
@@ -84,10 +86,10 @@ On Windows from Apache httpd 2.3.3 and l
        tcp(7)</a> man page.</p>
 
     <p>The default values on Windows are:</p>
-    <example>
-        AcceptFilter http data <br/>
-        AcceptFilter https data
-    </example>
+    <highlight language="config">
+AcceptFilter http data
+AcceptFilter https data
+    </highlight>
 
     <p>Window's mpm_winnt interprets the AcceptFilter to toggle the AcceptEx()
        API, and does not support http protocol buffering.  There are two values
@@ -107,7 +109,7 @@ On Windows from Apache httpd 2.3.3 and l
        filters.</p>
 
 </usage>
-<seealso><directive>Protocol</directive></seealso>
+<seealso><directive module="core">Protocol</directive></seealso>
 </directivesynopsis>
 
 <directivesynopsis>
@@ -170,15 +172,13 @@ On Windows from Apache httpd 2.3.3 and l
     the request, so you can use the following configuration to enable
     such a script:</p>
 
-    <example>
-      &lt;Files "mypaths.shtml"&gt;<br />
-      <indent>
-        Options +Includes<br />
-        SetOutputFilter INCLUDES<br />
-        AcceptPathInfo On<br />
-      </indent>
-      &lt;/Files&gt;
-    </example>
+    <highlight language="config">
+&lt;Files "mypaths.shtml"&gt;
+  Options +Includes
+  SetOutputFilter INCLUDES
+  AcceptPathInfo On
+&lt;/Files&gt;
+    </highlight>
 
 </usage>
 </directivesynopsis>
@@ -198,9 +198,7 @@ On Windows from Apache httpd 2.3.3 and l
     configuration files are <a href="#allowoverride">enabled for that
     directory</a>. For example:</p>
 
-    <example>
-      AccessFileName .acl
-    </example>
+    <highlight language="config">AccessFileName .acl</highlight>
 
     <p>before returning the document
     <code>/usr/local/web/index.html</code>, the server will read
@@ -208,13 +206,11 @@ On Windows from Apache httpd 2.3.3 and l
     <code>/usr/local/.acl</code> and <code>/usr/local/web/.acl</code>
     for directives, unless they have been disabled with</p>
 
-    <example>
-      &lt;Directory /&gt;<br />
-      <indent>
-        AllowOverride None<br />
-      </indent>
-      &lt;/Directory&gt;
-    </example>
+    <highlight language="config">
+&lt;Directory /&gt;
+    AllowOverride None
+&lt;/Directory&gt;
+    </highlight>
 </usage>
 <seealso><directive module="core">AllowOverride</directive></seealso>
 <seealso><a href="../configuring.html">Configuration Files</a></seealso>
@@ -247,9 +243,7 @@ content-type is <code>text/plain</code> 
     charset values</a> for use in Internet media types (MIME types).
     For example:</p>
 
-    <example>
-      AddDefaultCharset utf-8
-    </example>
+    <highlight language="config">AddDefaultCharset utf-8</highlight>
 
     <p><directive>AddDefaultCharset</directive> should only be used when all
     of the text resources to which it applies are known to be in that
@@ -460,9 +454,7 @@ NoDecode option available in 2.3.12 and 
 
     <p>Example:</p>
 
-    <example>
-      AllowOverride AuthConfig Indexes
-    </example>
+    <highlight language="config">AllowOverride AuthConfig Indexes</highlight>
 
     <p>In the example above all directives that are neither in the group
     <code>AuthConfig</code> nor <code>Indexes</code> cause an internal
@@ -514,10 +506,10 @@ NoDecode option available in 2.3.12 and 
 
     <p>Example:</p>
 
-    <example>
-      AllowOverride None<br />
-      AllowOverrideList Redirect RedirectMatch
-    </example>
+    <highlight language="config">
+AllowOverride None
+AllowOverrideList Redirect RedirectMatch
+    </highlight>
 
     <p>In the example above only the <code>Redirect</code> and
     <code>RedirectMatch</code> directives are allowed. All others will
@@ -525,10 +517,10 @@ NoDecode option available in 2.3.12 and 
 
     <p>Example:</p>
 
-    <example>
-      AllowOverride AuthConfig<br />
-      AllowOverrideList CookieTracking CookieName
-    </example>
+    <highlight language="config">
+AllowOverride AuthConfig
+AllowOverrideList CookieTracking CookieName
+    </highlight>
 
     <p>In the example above <directive module="core">AllowOverride
     </directive> grants permission to the <code>AuthConfig</code>
@@ -617,9 +609,10 @@ headers</description>
     (shared memory, locks, etc.). If set as a relative path, the full path
     will be relative to <directive>ServerRoot</directive></p>
 
-    <example><title>Example</title>
-      DefaultRuntimeDir scratch/
-    </example>
+    <p><strong>Example</strong></p>
+   <highlight language="config">
+DefaultRuntimeDir scratch/
+    </highlight>
 
     <p>The default location of <directive>DefaultRuntimeDir</directive> may be
     modified by changing the <code>DEFAULT_REL_RUNTIMEDIR</code> #define
@@ -655,9 +648,7 @@ which no other media type configuration 
     of configuration files, it may be specified with the value
     <code>none</code>, meaning no default media type. For example:</p>
 
-    <example>
-      DefaultType None
-    </example>
+    <highlight language="config">DefaultType None</highlight>
 
     <p><code>DefaultType None</code> is only available in
     httpd-2.2.7 and later.</p>
@@ -692,15 +683,15 @@ which no other media type configuration 
     the <code>${VAR}</code> syntax. The variable is always globally defined
     and not limited to the scope of the surrounding config section.</p>
 
-    <example>
-      &lt;IfDefine TEST&gt;<br/>
-      &nbsp;&nbsp;Define servername test.example.com<br/>
-      &lt;/IfDefine&gt;<br/>
-      &lt;IfDefine !TEST&gt;<br/>
-      &nbsp;&nbsp;Define servername www.example.com<br/>
-      &nbsp;&nbsp;Define SSL<br/>
-      &lt;/IfDefine&gt;<br/>
-    </example>
+    <highlight language="config">
+&lt;IfDefine TEST&gt;
+  Define servername test.example.com
+&lt;/IfDefine&gt;
+&lt;IfDefine !TEST&gt;
+  Define servername www.example.com
+  Define SSL
+&lt;/IfDefine&gt;
+    </highlight>
 
     <p>Variable names may not contain colon ":" characters, to avoid clashes
     with <directive module="mod_rewrite">RewriteMap</directive>'s syntax.</p>
@@ -732,13 +723,11 @@ named file-system directory, sub-directo
     <code>/home/user/public_html</code>, but <code>&lt;Directory
     /home/*/public_html&gt;</code> will match. Example:</p>
 
-    <example>
-      &lt;Directory /usr/local/httpd/htdocs&gt;<br />
-      <indent>
-        Options Indexes FollowSymLinks<br />
-      </indent>
-      &lt;/Directory&gt;
-    </example>
+    <highlight language="config">
+&lt;Directory "/usr/local/httpd/htdocs"&gt;
+  Options Indexes FollowSymLinks
+&lt;/Directory&gt;
+    </highlight>
 
     <note>
       <p>Be careful with the <var>directory-path</var> arguments:
@@ -753,9 +742,11 @@ named file-system directory, sub-directo
     expressions</glossary> can also be used, with the addition of the
     <code>~</code> character. For example:</p>
 
-    <example>
-      &lt;Directory ~ "^/www/.*/[0-9]{3}"&gt;
-    </example>
+    <highlight language="config">
+&lt;Directory ~ "^/www/.*/[0-9]{3}"&gt;
+
+&lt;/Directory&gt;
+</highlight>
 
     <p>would match directories in <code>/www/</code> that consisted of
     three numbers.</p>
@@ -768,19 +759,15 @@ named file-system directory, sub-directo
     href="#accessfilename">.htaccess</a> files. For example,
     with</p>
 
-    <example>
-      &lt;Directory /&gt;<br />
-      <indent>
-        AllowOverride None<br />
-      </indent>
-      &lt;/Directory&gt;<br />
-      <br />
-      &lt;Directory /home&gt;<br />
-      <indent>
-        AllowOverride FileInfo<br />
-      </indent>
-      &lt;/Directory&gt;
-    </example>
+    <highlight language="config">
+&lt;Directory /&gt;
+  AllowOverride None
+&lt;/Directory&gt;
+
+&lt;Directory "/home"&gt;
+  AllowOverride FileInfo
+&lt;/Directory&gt;
+    </highlight>
 
     <p>for access to the document <code>/home/web/dir/doc.html</code>
     the steps are:</p>
@@ -802,13 +789,11 @@ named file-system directory, sub-directo
     expressions are tested in the order they appeared in the
     configuration file. For example, with</p>
 
-    <example>
-      &lt;Directory ~ abc$&gt;<br />
-      <indent>
-        # ... directives here ...<br />
-      </indent>
-      &lt;/Directory&gt;
-    </example>
+    <highlight language="config">
+&lt;Directory ~ "abc$"&gt;
+  # ... directives here ...
+&lt;/Directory&gt;
+    </highlight>
 
     <p>the regular expression section won't be considered until after
     all normal <directive type="section">Directory</directive>s and
@@ -823,13 +808,11 @@ named file-system directory, sub-directo
     recommended that you change this with a block such
     as</strong></p>
 
-    <example>
-      &lt;Directory /&gt;<br />
-      <indent>
-        Require all denied<br />
-      </indent>
-      &lt;/Directory&gt;
-    </example>
+    <highlight language="config">
+&lt;Directory /&gt;
+  Require all denied
+&lt;/Directory&gt;
+    </highlight>
 
     <p><strong>and then override this for directories you
     <em>want</em> accessible. See the <a
@@ -865,9 +848,11 @@ the contents of file-system directories 
     However, it takes as an argument a
     <glossary ref="regex">regular expression</glossary>.  For example:</p>
 
-    <example>
-      &lt;DirectoryMatch "^/www/(.+/)?[0-9]{3}"&gt;
-    </example>
+    <highlight language="config">
+&lt;DirectoryMatch "^/www/(.+/)?[0-9]{3}"&gt;
+    # ...
+&lt;/DirectoryMatch&gt;
+</highlight>
 
     <p>would match directories in <code>/www/</code> that consisted of three
     numbers.</p>
@@ -911,9 +896,7 @@ from the web</description>
     path from the requested URL to the document root to make the
     path to the document. Example:</p>
 
-    <example>
-      DocumentRoot /usr/web
-    </example>
+    <highlight language="config">DocumentRoot "/usr/web"</highlight>
 
     <p>then an access to
     <code>http://my.example.com/index.html</code> refers to
@@ -948,14 +931,14 @@ satisfied by a request at runtime</descr
     in the same scope has not been applied.
     For example: In </p>
 
-    <example>
-        &lt;If "-z req('Host')"&gt;<br/>
-        ...<br/>
-        &lt;/If&gt;<br/>
-        &lt;Else&gt;<br/>
-        ...<br/>
-        &lt;/Else&gt;<br/>
-    </example>
+    <highlight language="config">
+&lt;If "-z req('Host')"&gt;
+  # ...
+&lt;/If&gt;
+&lt;Else&gt;
+  # ...
+&lt;/Else&gt;
+    </highlight>
 
     <p> The <directive type="section">If</directive> would match HTTP/1.0
         requests without a <var>Host:</var> header and the
@@ -993,17 +976,17 @@ satisfied</description>
     <directive type="section">ElseIf</directive> section in the same scope has
     not been applied.  For example: In </p>
 
-    <example>
-        &lt;If "-R '10.1.0.0/16'"&gt;<br/>
-        ...<br/>
-        &lt;/If&gt;<br/>
-        &lt;ElseIf "-R '10.0.0.0/8'"&gt;<br/>
-        ...<br/>
-        &lt;/ElseIf&gt;<br/>
-        &lt;Else&gt;<br/>
-        ...<br/>
-        &lt;/Else&gt;<br/>
-    </example>
+    <highlight language="config">
+&lt;If "-R '10.1.0.0/16'"&gt;
+  #...
+&lt;/If&gt;
+&lt;ElseIf "-R '10.0.0.0/8'"&gt;
+  #...
+&lt;/ElseIf&gt;
+&lt;Else&gt;
+  #...
+&lt;/Else&gt;
+    </highlight>
 
     <p>The <directive type="section">ElseIf</directive> would match if
     the remote address of a request belongs to the subnet 10.0.0.0/8 but
@@ -1058,20 +1041,16 @@ for a complete reference and more exampl
     <p>For server configurations that are vulnerable to these problems,
     you should disable memory-mapping of delivered files by specifying:</p>
 
-    <example>
-      EnableMMAP Off
-    </example>
+    <highlight language="config">EnableMMAP Off</highlight>
 
     <p>For NFS mounted files, this feature may be disabled explicitly for
     the offending files by specifying:</p>
 
-    <example>
-      &lt;Directory "/path-to-nfs-files"&gt;
-      <indent>
-        EnableMMAP Off
-      </indent>
-      &lt;/Directory&gt;
-    </example>
+    <highlight language="config">
+&lt;Directory "/path-to-nfs-files"&gt;
+  EnableMMAP Off
+&lt;/Directory&gt;
+    </highlight>
 </usage>
 </directivesynopsis>
 
@@ -1118,20 +1097,16 @@ version 2.3.9.</compatibility>
     <p>For server configurations that are not vulnerable to these problems,
     you may enable this feature by specifying:</p>
 
-    <example>
-      EnableSendfile On
-    </example>
+    <highlight language="config">EnableSendfile On</highlight>
 
     <p>For network mounted files, this feature may be disabled explicitly
     for the offending files by specifying:</p>
 
-    <example>
-      &lt;Directory "/path-to-nfs-files"&gt;
-      <indent>
-        EnableSendfile Off
-      </indent>
-      &lt;/Directory&gt;
-    </example>
+    <highlight language="config">
+&lt;Directory "/path-to-nfs-files"&gt;
+  EnableSendfile Off
+&lt;/Directory&gt;
+    </highlight>
     <p>Please note that the per-directory and .htaccess configuration
        of <directive>EnableSendfile</directive> is not supported by
        <module>mod_cache_disk</module>.
@@ -1156,24 +1131,25 @@ version 2.3.9.</compatibility>
     configuration parsing.  The typical use is for reporting required
     modules which are missing from the configuration.</p>
 
-    <example><title>Example</title>
-      # ensure that mod_include is loaded<br />
-      &lt;IfModule !include_module&gt;<br />
-      Error mod_include is required by mod_foo.  Load it with LoadModule.<br />
-      &lt;/IfModule&gt;<br />
-      <br />
-      # ensure that exactly one of SSL,NOSSL is defined<br />
-      &lt;IfDefine SSL&gt;<br />
-      &lt;IfDefine NOSSL&gt;<br />
-      Error Both SSL and NOSSL are defined.  Define only one of them.<br />
-      &lt;/IfDefine&gt;<br />
-      &lt;/IfDefine&gt;<br />
-      &lt;IfDefine !SSL&gt;<br />
-      &lt;IfDefine !NOSSL&gt;<br />
-      Error Either SSL or NOSSL must be defined.<br />
-      &lt;/IfDefine&gt;<br />
-      &lt;/IfDefine&gt;<br />
-    </example>
+    <highlight language="config">
+# Example
+# ensure that mod_include is loaded
+&lt;IfModule !include_module&gt;
+  Error "mod_include is required by mod_foo.  Load it with LoadModule."
+&lt;/IfModule&gt;
+
+# ensure that exactly one of SSL,NOSSL is defined
+&lt;IfDefine SSL&gt;
+&lt;IfDefine NOSSL&gt;
+  Error "Both SSL and NOSSL are defined.  Define only one of them."
+&lt;/IfDefine&gt;
+&lt;/IfDefine&gt;
+&lt;IfDefine !SSL&gt;
+&lt;IfDefine !NOSSL&gt;
+  Error "Either SSL or NOSSL must be defined."
+&lt;/IfDefine&gt;
+&lt;/IfDefine&gt;
+    </highlight>
 
 </usage>
 </directivesynopsis>
@@ -1215,13 +1191,13 @@ in case of an error</description>
     full URL which the client can resolve. Alternatively, a message
     can be provided to be displayed by the browser. Examples:</p>
 
-    <example>
-      ErrorDocument 500 http://foo.example.com/cgi-bin/tester<br />
-      ErrorDocument 404 /cgi-bin/bad_urls.pl<br />
-      ErrorDocument 401 /subscription_info.html<br />
-      ErrorDocument 403 "Sorry can't allow you access today"<br />
-      ErrorDocument 403 Forbidden!
-    </example>
+    <highlight language="config">
+ErrorDocument 500 http://foo.example.com/cgi-bin/tester
+ErrorDocument 404 /cgi-bin/bad_urls.pl
+ErrorDocument 401 /subscription_info.html
+ErrorDocument 403 "Sorry can't allow you access today"
+ErrorDocument 403 Forbidden!
+    </highlight>
 
     <p>Additionally, the special value <code>default</code> can be used
     to specify Apache httpd's simple hardcoded message.  While not required
@@ -1229,14 +1205,13 @@ in case of an error</description>
     Apache httpd's simple hardcoded message for configurations that would
     otherwise inherit an existing <directive>ErrorDocument</directive>.</p>
 
-    <example>
-      ErrorDocument 404 /cgi-bin/bad_urls.pl<br /><br />
-      &lt;Directory /web/docs&gt;<br />
-      <indent>
-        ErrorDocument 404 default<br />
-      </indent>
-      &lt;/Directory&gt;
-    </example>
+    <highlight language="config">
+ErrorDocument 404 /cgi-bin/bad_urls.pl
+
+&lt;Directory /web/docs&gt;
+  ErrorDocument 404 default
+&lt;/Directory&gt;
+    </highlight>
 
     <p>Note that when you specify an <directive>ErrorDocument</directive>
     that points to a remote URL (ie. anything with a method such as
@@ -1264,7 +1239,7 @@ in case of an error</description>
     href="http://support.microsoft.com/default.aspx?scid=kb;en-us;Q294807"
     >Q294807</a>.</p>
 
-    <p>Although most error messages can be overriden, there are certain
+    <p>Although most error messages can be overridden, there are certain
     circumstances where the internal messages are used regardless of the
     setting of <directive module="core">ErrorDocument</directive>.  In
     particular, if a malformed request is detected, normal request processing
@@ -1296,17 +1271,13 @@ in case of an error</description>
     the <var>file-path</var> is not absolute then it is assumed to be
     relative to the <directive module="core">ServerRoot</directive>.</p>
 
-    <example><title>Example</title>
-    ErrorLog /var/log/httpd/error_log
-    </example>
+    <highlight language="config">ErrorLog "/var/log/httpd/error_log"</highlight>
 
     <p>If the <var>file-path</var>
     begins with a pipe character "<code>|</code>" then it is assumed to be a
     command to spawn to handle the error log.</p>
 
-    <example><title>Example</title>
-    ErrorLog "|/usr/local/bin/httpd_errors"
-    </example>
+    <highlight language="config">ErrorLog "|/usr/local/bin/httpd_errors"</highlight>
 
     <p>See the notes on <a href="../logs.html#piped">piped logs</a> for
     more information.</p>
@@ -1320,9 +1291,7 @@ in case of an error</description>
     in individual virtual hosts, the final facility specified affects the
     entire server.</p>
 
-    <example><title>Example</title>
-    ErrorLog syslog:user
-    </example>
+    <highlight language="config">ErrorLog syslog:user</highlight>
 
     <p>SECURITY: See the <a
     href="../misc/security_tips.html#serverroot">security tips</a>
@@ -1353,9 +1322,10 @@ in case of an error</description>
     supplementary information is logged in the error log in addition to the
     actual log message.</p>
 
-    <example><title>Simple example</title>
-        ErrorLogFormat "[%t] [%l] [pid %P] %F: %E: [client %a] %M"
-    </example>
+    <highlight language="config">
+#Simple example
+ErrorLogFormat "[%t] [%l] [pid %P] %F: %E: [client %a] %M"
+    </highlight>
 
     <p>Specifying <code>connection</code> or <code>request</code> as first
     parameter allows to specify additional formats, causing additional
@@ -1369,11 +1339,11 @@ in case of an error</description>
     example, the Referer header is only present if the log message is
     associated to a request and the log message happens at a time when the
     Referer header has already been read from the client.  If no output is
-    produced, the default behavior is to delete everything from the preceeding
+    produced, the default behavior is to delete everything from the preceding
     space character to the next space character.  This means the log line is
     implicitly divided into fields on non-whitespace to whitespace transitions.
     If a format string item does not produce output, the whole field is
-    ommitted.  For example, if the remote address <code>%a</code> in the log
+    omitted.  For example, if the remote address <code>%a</code> in the log
     format <code>[%t] [%l] [%a] %M&nbsp;</code> is not available, the surrounding
     brackets are not logged either.  Space characters can be escaped with a
     backslash to prevent them from delimiting a field.  The combination '%&nbsp;'
@@ -1385,7 +1355,7 @@ in case of an error</description>
     respective item does not produce any output. In once-per-connection/request
     formats, it is also possible to use the <code>+</code> (plus) modifier. If an
     item with the plus modifier does not produce any output, the whole line is
-    ommitted.</p>
+    omitted.</p>
 
     <p>A number as modifier can be used to assign a log severity level to a
     format item. The item will only be logged if the severity of the log
@@ -1519,32 +1489,33 @@ in case of an error</description>
     with error log lines. If <module>mod_unique_id</module> is loaded, its
     unique id will be used as log ID for requests.</p>
 
-    <example><title>Example (default format)</title>
-        ErrorLogFormat "[%{u}t] [%-m:%l] [pid %P:tid %T] %7F: %E: [client\ %a]
-        %M%&nbsp;,\&nbsp;referer\&nbsp;%{Referer}i"
-    </example>
+    <highlight language="config">
+#Example (default format)
+ErrorLogFormat "[%{u}t] [%-m:%l] [pid %P:tid %T] %7F: %E: [client\ %a] %M%&nbsp;,\&nbsp;referer\&nbsp;%{Referer}i"
+    </highlight>
 
     <p>This would result in error messages such as:</p>
 
-    <example>
+	<example>
     [Thu May 12 08:28:57.652118 2011] [core:error] [pid 8777:tid 4326490112] [client ::1:58619] File does not exist: /usr/local/apache2/htdocs/favicon.ico
     </example>
 
-    <p>Notice that, as discussed above, some fields are ommitted
+    <p>Notice that, as discussed above, some fields are omitted
     entirely because they are not defined.</p>
 
-    <example><title>Example (similar to the 2.2.x format)</title>
-        ErrorLogFormat "[%t] [%l] %7F: %E: [client\ %a]
-        %M%&nbsp;,\&nbsp;referer\&nbsp;%{Referer}i"
-    </example>
-
-    <example><title>Advanced example with request/connection log IDs</title>
-        ErrorLogFormat "[%{uc}t] [%-m:%-l] [R:%L] [C:%{C}L] %7F: %E: %M"<br/>
-        ErrorLogFormat request "[%{uc}t] [R:%L] Request %k on C:%{c}L pid:%P tid:%T"<br/>
-        ErrorLogFormat request "[%{uc}t] [R:%L] UA:'%+{User-Agent}i'"<br/>
-        ErrorLogFormat request "[%{uc}t] [R:%L] Referer:'%+{Referer}i'"<br/>
-        ErrorLogFormat connection "[%{uc}t] [C:%{c}L] local\ %a remote\ %A"<br/>
-    </example>
+    <highlight language="config">
+#Example (similar to the 2.2.x format)
+ErrorLogFormat "[%t] [%l] %7F: %E: [client\ %a] %M%&nbsp;,\&nbsp;referer\&nbsp;%{Referer}i"
+    </highlight>
+
+    <highlight language="config">
+#Advanced example with request/connection log IDs
+ErrorLogFormat "[%{uc}t] [%-m:%-l] [R:%L] [C:%{C}L] %7F: %E: %M"
+ErrorLogFormat request "[%{uc}t] [R:%L] Request %k on C:%{c}L pid:%P tid:%T"
+ErrorLogFormat request "[%{uc}t] [R:%L] UA:'%+{User-Agent}i'"
+ErrorLogFormat request "[%{uc}t] [R:%L] Referer:'%+{Referer}i'"
+ErrorLogFormat connection "[%{uc}t] [C:%{c}L] local\ %a remote\ %A"
+    </highlight>
 
 </usage>
 <seealso><directive module="core">ErrorLog</directive></seealso>
@@ -1619,7 +1590,7 @@ earlier.</compatibility>
      <dd>The number of bytes in the file will be included</dd>
      <dt><strong>All</strong></dt>
      <dd>All available fields will be used. This is equivalent to:
-         <example>FileETag INode MTime Size</example></dd>
+         <highlight language="config">FileETag INode MTime Size</highlight></dd>
      <dt><strong>None</strong></dt>
      <dd>If a document is file-based, no <code>ETag</code> field will be
        included in the response</dd>
@@ -1690,9 +1661,11 @@ filenames</description>
     can also be used, with the addition of the
     <code>~</code> character. For example:</p>
 
-    <example>
-      &lt;Files ~ "\.(gif|jpe?g|png)$"&gt;
-    </example>
+    <highlight language="config">
+&lt;Files ~ "\.(gif|jpe?g|png)$"&gt;
+    #...
+&lt;/Files&gt;
+</highlight>
 
     <p>would match most common Internet graphics formats. <directive
     module="core" type="section">FilesMatch</directive> is preferred,
@@ -1728,9 +1701,11 @@ filenames</description>
     does. However, it accepts a <glossary ref="regex">regular
     expression</glossary>. For example:</p>
 
-    <example>
-      &lt;FilesMatch "\.(gif|jpe?g|png)$"&gt;
-    </example>
+<highlight language="config">
+&lt;FilesMatch "\.(gif|jpe?g|png)$"&gt;
+    # ...
+&lt;/FilesMatch&gt;
+</highlight>
 
     <p>would match most common Internet graphics formats.</p>
 </usage>
@@ -1761,9 +1736,7 @@ media type in the HTTP Content-Type head
     GIF files, but did not want to label them all with <code>.gif</code>,
     you might want to use:</p>
 
-    <example>
-      ForceType image/gif
-    </example>
+    <highlight language="config">ForceType image/gif</highlight>
 
     <p>Note that this directive overrides other indirect media type
     associations defined in mime.types or via the
@@ -1773,21 +1746,17 @@ media type in the HTTP Content-Type head
     <directive>ForceType</directive> settings
     by using the value of <code>None</code>:</p>
 
-    <example>
-      # force all files to be image/gif:<br />
-      &lt;Location /images&gt;<br />
-        <indent>
-          ForceType image/gif<br />
-        </indent>
-      &lt;/Location&gt;<br />
-      <br />
-      # but normal mime-type associations here:<br />
-      &lt;Location /images/mixed&gt;<br />
-      <indent>
-        ForceType None<br />
-      </indent>
-      &lt;/Location&gt;
-    </example>
+    <highlight language="config">
+# force all files to be image/gif:
+&lt;Location /images&gt;
+  ForceType image/gif
+&lt;/Location&gt;
+
+# but normal mime-type associations here:
+&lt;Location /images/mixed&gt;
+  ForceType None
+&lt;/Location&gt;
+    </highlight>
 
     <p>This directive primarily overrides the content types generated for
     static files served out of the filesystem.  For resources other than
@@ -1804,7 +1773,7 @@ media type in the HTTP Content-Type head
 </contextlist>
 
 <usage>
-    <p>When the server has been compiled with gprof profiling suppport,
+    <p>When the server has been compiled with gprof profiling support,
     <directive>GprofDir</directive> causes <code>gmon.out</code> files to
     be written to the specified directory when the process exits.  If the
     argument ends with a percent symbol ('%'), subdirectories are created
@@ -1877,9 +1846,7 @@ satisfied by a request at runtime</descr
     directives if and only if the expression evaluates to true.
     For example:</p>
 
-    <example>
-        &lt;If "-z req('Host')"&gt;
-    </example>
+    <highlight language="config">&lt;If "-z req('Host')"&gt;</highlight>
 
     <p>would match HTTP/1.0 requests without a <var>Host:</var> header.
     Expressions may contain various shell-like operators for string
@@ -1888,9 +1855,7 @@ satisfied by a request at runtime</descr
     and others (<code>-n</code>, <code>-z</code>, <code>-f</code>, ...).
     It is also possible to use regular expressions, </p>
 
-    <example>
-        &lt;If "%{QUERY_STRING} =~ /(delete|commit)=.*?elem/"&gt;
-    </example>
+    <highlight language="config">&lt;If "%{QUERY_STRING} =~ /(delete|commit)=.*?elem/"&gt;</highlight>
 
     <p>shell-like pattern matches and many other operations. These operations
     can be done on request headers (<code>req</code>), environment variables
@@ -1955,32 +1920,22 @@ if a test is true at startup</descriptio
     nest-able, which can be used to implement simple
     multiple-parameter tests. Example:</p>
 
-    <example>
-      httpd -DReverseProxy -DUseCache -DMemCache ...<br />
-      <br />
-      # httpd.conf<br />
-      &lt;IfDefine ReverseProxy&gt;<br />
-      <indent>
-        LoadModule proxy_module   modules/mod_proxy.so<br />
-        LoadModule proxy_http_module   modules/mod_proxy_http.so<br />
-        &lt;IfDefine UseCache&gt;<br />
-        <indent>
-          LoadModule cache_module   modules/mod_cache.so<br />
-          &lt;IfDefine MemCache&gt;<br />
-          <indent>
-            LoadModule mem_cache_module   modules/mod_mem_cache.so<br />
-          </indent>
-          &lt;/IfDefine&gt;<br />
-          &lt;IfDefine !MemCache&gt;<br />
-          <indent>
-            LoadModule cache_disk_module   modules/mod_cache_disk.so<br />
-          </indent>
-          &lt;/IfDefine&gt;
-        </indent>
-        &lt;/IfDefine&gt;
-      </indent>
-      &lt;/IfDefine&gt;
-    </example>
+    <example>httpd -DReverseProxy -DUseCache -DMemCache ...</example>
+    <highlight language="config">
+&lt;IfDefine ReverseProxy&gt;
+  LoadModule proxy_module   modules/mod_proxy.so
+  LoadModule proxy_http_module   modules/mod_proxy_http.so
+  &lt;IfDefine UseCache&gt;
+    LoadModule cache_module   modules/mod_cache.so
+    &lt;IfDefine MemCache&gt;
+      LoadModule mem_cache_module   modules/mod_mem_cache.so
+    &lt;/IfDefine&gt;
+    &lt;IfDefine !MemCache&gt;
+      LoadModule cache_disk_module   modules/mod_cache_disk.so
+    &lt;/IfDefine&gt;
+  &lt;/IfDefine&gt;
+&lt;/IfDefine&gt;
+    </highlight>
 </usage>
 </directivesynopsis>
 
@@ -2077,33 +2032,29 @@ wildcard matching available in 2.3.6 and
 
     <p>Examples:</p>
 
-    <example>
-      Include /usr/local/apache2/conf/ssl.conf<br />
-      Include /usr/local/apache2/conf/vhosts/*.conf
-    </example>
+    <highlight language="config">
+Include /usr/local/apache2/conf/ssl.conf
+Include /usr/local/apache2/conf/vhosts/*.conf
+    </highlight>
 
     <p>Or, providing paths relative to your <directive
     module="core">ServerRoot</directive> directory:</p>
 
-    <example>
-      Include conf/ssl.conf<br />
-      Include conf/vhosts/*.conf
-    </example>
+    <highlight language="config">
+Include conf/ssl.conf
+Include conf/vhosts/*.conf
+    </highlight>
 
     <p>Wildcards may be included in the directory or file portion of the
     path. This example will fail if there is no subdirectory in conf/vhosts
     that contains at least one *.conf file:</p>
 
-    <example>
-      Include conf/vhosts/*/*.conf
-    </example>
+    <highlight language="config">Include conf/vhosts/*/*.conf</highlight>
 
     <p>Alternatively, the following command will just be ignored in case of
     missing files or directories:</p>
 
-    <example>
-      IncludeOptional conf/vhosts/*/*.conf
-    </example>
+    <highlight language="config">IncludeOptional conf/vhosts/*/*.conf</highlight>
 
 </usage>
 
@@ -2226,13 +2177,11 @@ methods</description>
     only to the methods <code>POST</code>, <code>PUT</code>, and
     <code>DELETE</code>, leaving all other methods unprotected:</p>
 
-    <example>
-      &lt;Limit POST PUT DELETE&gt;<br />
-      <indent>
-        Require valid-user<br />
-      </indent>
-      &lt;/Limit&gt;
-    </example>
+    <highlight language="config">
+&lt;Limit POST PUT DELETE&gt;
+  Require valid-user
+&lt;/Limit&gt;
+    </highlight>
 
     <p>The method names listed can be one or more of: <code>GET</code>,
     <code>POST</code>, <code>PUT</code>, <code>DELETE</code>,
@@ -2272,18 +2221,14 @@ methods</description>
     <code>Require group editors</code> directive will be ignored
     in all cases:</p>
 
-    <example>
-      &lt;LimitExcept GET&gt;
-      <indent>
-        Require valid-user
-      </indent>
-      &lt;/LimitExcept&gt;<br />
-      &lt;Limit POST&gt;
-      <indent>
-        Require group editors
-      </indent>
-      &lt;/Limit&gt;
-    </example>
+    <highlight language="config">
+&lt;LimitExcept GET&gt;
+  Require valid-user
+&lt;/LimitExcept&gt;
+&lt;Limit POST&gt;
+  Require group editors
+&lt;/Limit&gt;
+    </highlight>
 </usage>
 </directivesynopsis>
 
@@ -2310,13 +2255,11 @@ except the named ones</description>
 
     <p>For example:</p>
 
-    <example>
-      &lt;LimitExcept POST GET&gt;<br />
-      <indent>
-        Require valid-user<br />
-      </indent>
-      &lt;/LimitExcept&gt;
-    </example>
+    <highlight language="config">
+&lt;LimitExcept POST GET&gt;
+  Require valid-user
+&lt;/LimitExcept&gt;
+    </highlight>
 
 </usage>
 </directivesynopsis>
@@ -2350,9 +2293,7 @@ subrequests</description>
     determines, how deep subrequests may be nested. If you specify only one
     <var>number</var>, it will be assigned to both limits.</p>
 
-    <example><title>Example</title>
-      LimitInternalRecursion 5
-    </example>
+    <highlight language="config">LimitInternalRecursion 5</highlight>
 </usage>
 </directivesynopsis>
 
@@ -2395,9 +2336,7 @@ from the client</description>
     location, and wish to limit the size of the uploaded file to 100K,
     you might use the following directive:</p>
 
-    <example>
-      LimitRequestBody 102400
-    </example>
+    <highlight language="config">LimitRequestBody 102400</highlight>
 
     <note><p>For a full description of how this directive is interpreted by
     proxy requests, see the <module>mod_proxy</module> documentation.</p>
@@ -2440,9 +2379,7 @@ will be accepted from the client</descri
 
     <p>For example:</p>
 
-    <example>
-      LimitRequestFields 50
-    </example>
+    <highlight language="config">LimitRequestFields 50</highlight>
 
      <note type="warning"><title>Warning</title>
      <p> When name-based virtual hosting is used, the value for this
@@ -2481,9 +2418,7 @@ client</description>
 
     <p>For example:</p>
 
-    <example>
-      LimitRequestFieldSize 4094
-    </example>
+    <highlight language="config">LimitRequestFieldSize 4094</highlight>
 
     <note>Under normal conditions, the value should not be changed from
     the default. Also, you can't set this higher than 8190 without
@@ -2525,9 +2460,7 @@ from the client</description>
 
     <p>For example:</p>
 
-    <example>
-      LimitRequestLine 4094
-    </example>
+    <highlight language="config">LimitRequestLine 4094</highlight>
 
     <note>Under normal conditions, the value should not be changed from
     the default. Also, you can't set this higher than 8190 without
@@ -2557,9 +2490,7 @@ from the client</description>
 
     <p>Example:</p>
 
-    <example>
-      LimitXMLRequestBody 0
-    </example>
+    <highlight language="config">LimitXMLRequestBody 0</highlight>
 
 </usage>
 </directivesynopsis>
@@ -2610,19 +2541,21 @@ URLs</description>
     /private1, /private1/ and /private1/file.txt will have the enclosed
     directives applied, but /private1other would not.
     </p>
-    <example>
-      &lt;Location /private1&gt;
-          ...
-    </example>
+    <highlight language="config">
+&lt;Location /private1&gt;
+    #  ...
+&lt;/Location&gt;
+    </highlight>
     <p>
     In the example below, where a trailing slash is used, requests to
     /private2/ and /private2/file.txt will have the enclosed
     directives applied, but /private2 and /private2other would not.
     </p>
-    <example>
-      &lt;Location /private2<em>/</em>&gt;
-          ...
-    </example>
+    <highlight language="config">
+&lt;Location /private2<em>/</em>&gt;
+    # ...
+&lt;/Location&gt;
+    </highlight>
 
     <note><title>When to use <directive
     type="section">Location</directive></title>
@@ -2651,9 +2584,11 @@ URLs</description>
     can also be used, with the addition of the <code>~</code>
     character. For example:</p>
 
-    <example>
-      &lt;Location ~ "/(extra|special)/data"&gt;
-    </example>
+    <highlight language="config">
+&lt;Location ~ "/(extra|special)/data"&gt;
+    #...
+&lt;/Location&gt;
+</highlight>
 
     <p>would match URLs that contained the substring <code>/extra/data</code>
     or <code>/special/data</code>. The directive <directive
@@ -2669,14 +2604,12 @@ URLs</description>
     directive. For example, to enable status requests, but allow them
     only from browsers at <code>example.com</code>, you might use:</p>
 
-    <example>
-      &lt;Location /status&gt;<br />
-      <indent>
-        SetHandler server-status<br />
-        Require host example.com<br />
-      </indent>
-      &lt;/Location&gt;
-    </example>
+    <highlight language="config">
+&lt;Location /status&gt;
+  SetHandler server-status
+  Require host example.com
+&lt;/Location&gt;
+    </highlight>
 
     <note><title>Note about / (slash)</title>
       <p>The slash character has special meaning depending on where in a
@@ -2722,9 +2655,11 @@ matching URLs</description>
     it takes a <glossary ref="regex">regular expression</glossary>
     as an argument instead of a simple string. For example:</p>
 
-    <example>
-      &lt;LocationMatch "/(extra|special)/data"&gt;
-    </example>
+    <highlight language="config">
+&lt;LocationMatch "/(extra|special)/data"&gt;
+    # ...
+&lt;/LocationMatch&gt;
+</highlight>
 
     <p>would match URLs that contained the substring <code>/extra/data</code>
     or <code>/special/data</code>.</p>
@@ -2901,9 +2836,7 @@ matching URLs</description>
 
     <p>For example:</p>
 
-    <example>
-      LogLevel notice
-    </example>
+    <highlight language="config">LogLevel notice</highlight>
 
     <note><title>Note</title>
       <p>When logging to a regular file messages of the level
@@ -2920,20 +2853,20 @@ matching URLs</description>
     as module specification. This means the following three specifications
     are equivalent:</p>
 
-    <example>
-      LogLevel info ssl:warn<br />
-      LogLevel info mod_ssl.c:warn<br />
-      LogLevel info ssl_module:warn<br />
-    </example>
+    <highlight language="config">
+LogLevel info ssl:warn
+LogLevel info mod_ssl.c:warn
+LogLevel info ssl_module:warn
+    </highlight>
 
     <p>It is also possible to change the level per directory:</p>
 
-    <example>
-        LogLevel info<br />
-        &lt;Directory /usr/local/apache/htdocs/app&gt;<br />
-        &nbsp; LogLevel debug<br />
-        &lt;/Files&gt;
-    </example>
+    <highlight language="config">
+LogLevel info
+&lt;Directory "/usr/local/apache/htdocs/app"&gt;
+  LogLevel debug
+&lt;/Directory&gt;
+    </highlight>
 
     <note>
         Per directory loglevel configuration only affects messages that are
@@ -2963,9 +2896,7 @@ connection</description>
 
     <p>For example:</p>
 
-    <example>
-      MaxKeepAliveRequests 500
-    </example>
+    <highlight language="config">MaxKeepAliveRequests 500</highlight>
 </usage>
 </directivesynopsis>
 
@@ -3288,10 +3219,10 @@ or specified mutexes</description>
     <code>/var/httpd/locks</code>.  The mutex mechanism for all other mutexes
     will be changed from the compiled-in default to <code>sysvsem</code>.</p>
 
-    <example>
-    Mutex sysvsem default<br />
-    Mutex fcntl:/var/httpd/locks mpm-accept
-    </example>
+    <highlight language="config">
+Mutex sysvsem default
+Mutex fcntl:/var/httpd/locks mpm-accept
+    </highlight>
 </usage>
 </directivesynopsis>
 
@@ -3439,38 +3370,30 @@ directory</description>
 
     <p>For example, without any <code>+</code> and <code>-</code> symbols:</p>
 
-    <example>
-      &lt;Directory /web/docs&gt;<br />
-      <indent>
-        Options Indexes FollowSymLinks<br />
-      </indent>
-      &lt;/Directory&gt;<br />
-      <br />
-      &lt;Directory /web/docs/spec&gt;<br />
-      <indent>
-        Options Includes<br />
-      </indent>
-      &lt;/Directory&gt;
-    </example>
+    <highlight language="config">
+&lt;Directory "/web/docs"&gt;
+  Options Indexes FollowSymLinks
+&lt;/Directory&gt;
+
+&lt;Directory "/web/docs/spec"&gt;
+  Options Includes
+&lt;/Directory&gt;
+    </highlight>
 
     <p>then only <code>Includes</code> will be set for the
     <code>/web/docs/spec</code> directory. However if the second
     <directive>Options</directive> directive uses the <code>+</code> and
     <code>-</code> symbols:</p>
 
-    <example>
-      &lt;Directory /web/docs&gt;<br />
-      <indent>
-        Options Indexes FollowSymLinks<br />
-      </indent>
-      &lt;/Directory&gt;<br />
-      <br />
-      &lt;Directory /web/docs/spec&gt;<br />
-      <indent>
-        Options +Includes -Indexes<br />
-      </indent>
-      &lt;/Directory&gt;
-    </example>
+    <highlight language="config">
+&lt;Directory "/web/docs"&gt;
+  Options Indexes FollowSymLinks
+&lt;/Directory&gt;
+
+&lt;Directory "/web/docs/spec"&gt;
+  Options +Includes -Indexes
+&lt;/Directory&gt;
+    </highlight>
 
     <p>then the options <code>FollowSymLinks</code> and
     <code>Includes</code> are set for the <code>/web/docs/spec</code>
@@ -3505,13 +3428,11 @@ On Windows from Apache 2.3.3 and later.<
 
     <p>For example, if you are running <code>https</code> on a non-standard port, specify the protocol explicitly:</p>
 
-    <example>
-      Protocol https
-    </example>
+    <highlight language="config">Protocol https</highlight>
 
     <p>You can also specify the protocol using the <directive module="mpm_common">Listen</directive> directive.</p>
 </usage>
-<seealso><directive>AcceptFilter</directive></seealso>
+<seealso><directive module="core">AcceptFilter</directive></seealso>
 <seealso><directive module="mpm_common">Listen</directive></seealso>
 </directivesynopsis>
 
@@ -3643,15 +3564,11 @@ later</compatibility>
     by the shebang line (first line, starting with <code>#!</code>) in the
     script. On Win32 systems this line usually looks like:</p>
 
-    <example>
-      #!C:/Perl/bin/perl.exe
-    </example>
+    <highlight language="perl">#!C:/Perl/bin/perl.exe</highlight>
 
     <p>or, if <code>perl</code> is in the <code>PATH</code>, simply:</p>
 
-    <example>
-      #!perl
-    </example>
+    <highlight language="perl">#!perl</highlight>
 
     <p>Setting <code>ScriptInterpreterSource Registry</code> will
     cause the Windows Registry tree <code>HKEY_CLASSES_ROOT</code> to be
@@ -3747,9 +3664,7 @@ messages sent to the client</description
 
     <p>It may be worth setting up a dedicated address for this, e.g.</p>
 
-    <example>
-      ServerAdmin www-admin@foo.example.com
-    </example>
+    <highlight language="config">ServerAdmin www-admin@foo.example.com</highlight>
     <p>as users do not always mention that they are talking about the
     server!</p>
 </usage>
@@ -3768,18 +3683,18 @@ to name-virtual hosts</description>
     href="../vhosts/name-based.html">name-based virtual hosts</a>. The
     <directive>ServerAlias</directive> may include wildcards, if appropriate.</p>
 
-    <example>
-      &lt;VirtualHost *:80&gt;<br />
-      ServerName server.example.com<br />
-      ServerAlias server server2.example.com server2<br />
-      ServerAlias *.example.com<br />
-      UseCanonicalName Off<br />
-      # ...<br />
-      &lt;/VirtualHost&gt;
-    </example>
+    <highlight language="config">
+&lt;VirtualHost *:80&gt;
+  ServerName server.example.com
+  ServerAlias server server2.example.com server2
+  ServerAlias *.example.com
+  UseCanonicalName Off
+  # ...
+&lt;/VirtualHost&gt;
+    </highlight>
 
     <p>Name-based virtual hosts for the best-matching set of  <directive
-    type="section" module="core">virtualhost</directive>s are processsed
+    type="section" module="core">virtualhost</directive>s are processed
     in the order they appear in the configuration.  The first matching <directive
     module="core">ServerName</directive> or <directive module="core"
     >ServerAlias</directive> is used, with no different precedence for wildcards
@@ -3814,9 +3729,7 @@ itself</description>
     and you wish the web server to be so identified, the following
     directive should be used:</p>
 
-    <example>
-      ServerName www.example.com
-    </example>
+    <highlight language="config">ServerName www.example.com</highlight>
 
     <p>The <directive>ServerName</directive> directive
     may appear anywhere within the definition of a server. However,
@@ -3908,9 +3821,7 @@ is accessed by an incompatible browser</
     module="mod_so">LoadModule</directive>, for example) are taken as
     relative to this directory.</p>
 
-    <example><title>Example</title>
-      ServerRoot /home/httpd
-    </example>
+    <highlight language="config">ServerRoot "/home/httpd"</highlight>
 
     <p>The default location of <directive>ServerRoot</directive> may be
     modified by using the <code>--prefix</code> argument to
@@ -3980,7 +3891,7 @@ header</description>
     <dl>
       <dt><code>ServerTokens Full</code> (or not specified)</dt>
 
-      <dd>Server sends (<em>e.g.</em>): <code>Server: Apache/2.4.1
+      <dd>Server sends (<em>e.g.</em>): <code>Server: Apache/2.4.2
       (Unix) PHP/4.2.2 MyMod/1.2</code></dd>
 
       <dt><code>ServerTokens Prod[uctOnly]</code></dt>
@@ -4001,11 +3912,11 @@ header</description>
       <dt><code>ServerTokens Min[imal]</code></dt>
 
       <dd>Server sends (<em>e.g.</em>): <code>Server:
-      Apache/2.4.1</code></dd>
+      Apache/2.4.2</code></dd>
 
       <dt><code>ServerTokens OS</code></dt>
 
-      <dd>Server sends (<em>e.g.</em>): <code>Server: Apache/2.4.1
+      <dd>Server sends (<em>e.g.</em>): <code>Server: Apache/2.4.2
       (Unix)</code></dd>
 
     </dl>
@@ -4050,22 +3961,18 @@ handler</description>
     of extension, you might put the following into an
     <code>.htaccess</code> file in that directory:</p>
 
-    <example>
-      SetHandler imap-file
-    </example>
+    <highlight language="config">SetHandler imap-file</highlight>
 
     <p>Another example: if you wanted to have the server display a
     status report whenever a URL of
     <code>http://servername/status</code> was called, you might put
     the following into <code>httpd.conf</code>:</p>
 
-    <example>
-      &lt;Location /status&gt;<br />
-      <indent>
-        SetHandler server-status<br />
-      </indent>
-      &lt;/Location&gt;
-    </example>
+    <highlight language="config">
+&lt;Location "/status"&gt;
+  SetHandler server-status
+&lt;/Location&gt;
+    </highlight>
 
     <p>You can override an earlier defined <directive>SetHandler</directive>
     directive by using the value <code>None</code>.</p>
@@ -4127,13 +4034,11 @@ server</description>
     in the <code>/www/data/</code> directory for server-side
     includes.</p>
 
-    <example>
-      &lt;Directory /www/data/&gt;<br />
-      <indent>
-        SetOutputFilter INCLUDES<br />
-      </indent>
-      &lt;/Directory&gt;
-    </example>
+    <highlight language="config">
+&lt;Directory "/www/data/"&gt;
+  SetOutputFilter INCLUDES
+&lt;/Directory&gt;
+    </highlight>
 
     <p>If more than one filter is specified, they must be separated
     by semicolons in the order in which they should process the
@@ -4264,8 +4169,8 @@ port</description>
     authentication enabled, this will cause the user to have to
     authenticate twice (once for <code>www</code> and once again
     for <code>www.example.com</code> -- see <a
-    href="http://httpd.apache.org/docs/misc/FAQ.html#prompted-twice">the
-    FAQ on this subject for more information</a>). But if
+    href="http://wiki.apache.org/httpd/FAQ#Why_does_Apache_ask_for_my_password_twice_before_serving_a_file.3F">
+    the FAQ on this subject for more information</a>). But if
     <directive>UseCanonicalName</directive> is set <code>Off</code>, then
     Apache httpd will redirect to <code>http://www/splat/</code>.</p>
 
@@ -4374,34 +4279,30 @@ hostname or IP address</description>
 
     </ul>
 
-    <example><title>Example</title>
-      &lt;VirtualHost 10.1.2.3:80&gt;<br />
-      <indent>
-        ServerAdmin webmaster@host.example.com<br />
-        DocumentRoot /www/docs/host.example.com<br />
-        ServerName host.example.com<br />
-        ErrorLog logs/host.example.com-error_log<br />
-        TransferLog logs/host.example.com-access_log<br />
-      </indent>
-      &lt;/VirtualHost&gt;
-    </example>
+    <highlight language="config">
+&lt;VirtualHost 10.1.2.3:80&gt;
+  ServerAdmin webmaster@host.example.com
+  DocumentRoot /www/docs/host.example.com
+  ServerName host.example.com
+  ErrorLog logs/host.example.com-error_log
+  TransferLog logs/host.example.com-access_log
+&lt;/VirtualHost&gt;
+    </highlight>
 
 
     <p>IPv6 addresses must be specified in square brackets because
     the optional port number could not be determined otherwise.  An
     IPv6 example is shown below:</p>
 
-    <example>
-      &lt;VirtualHost [2001:db8::a00:20ff:fea7:ccea]:80&gt;<br />
-      <indent>
-        ServerAdmin webmaster@host.example.com<br />
-        DocumentRoot /www/docs/host.example.com<br />
-        ServerName host.example.com<br />
-        ErrorLog logs/host.example.com-error_log<br />
-        TransferLog logs/host.example.com-access_log<br />
-      </indent>
-      &lt;/VirtualHost&gt;
-    </example>
+    <highlight language="config">
+&lt;VirtualHost [2001:db8::a00:20ff:fea7:ccea]:80&gt;
+  ServerAdmin webmaster@host.example.com
+  DocumentRoot /www/docs/host.example.com
+  ServerName host.example.com
+  ErrorLog logs/host.example.com-error_log
+  TransferLog logs/host.example.com-access_log
+&lt;/VirtualHost&gt;
+    </highlight>
 
     <p>Each Virtual Host must correspond to a different IP address,
     different port number or a different host name for the server,

Modified: httpd/httpd/branches/2.4.x/docs/manual/mod/mod_access_compat.xml
URL: http://svn.apache.org/viewvc/httpd/httpd/branches/2.4.x/docs/manual/mod/mod_access_compat.xml?rev=1334008&r1=1334007&r2=1334008&view=diff
==============================================================================
--- httpd/httpd/branches/2.4.x/docs/manual/mod/mod_access_compat.xml (original)
+++ httpd/httpd/branches/2.4.x/docs/manual/mod/mod_access_compat.xml Fri May  4 14:59:59 2012
@@ -113,10 +113,10 @@ server</description>
       <dt>A (partial) domain-name</dt>
 
       <dd>
-      <example><title>Example:</title>
-        Allow from example.org<br />
-        Allow from .net example.edu
-      </example>
+      <highlight language="config">
+Allow from example.org
+Allow from .net example.edu
+      </highlight>
       <p>Hosts whose names match, or end in, this string are allowed
       access. Only complete components are matched, so the above
       example will match <code>foo.example.org</code> but it will not
@@ -133,37 +133,37 @@ server</description>
       <dt>A full IP address</dt>
 
       <dd>
-      <example><title>Example:</title>
-        Allow from 10.1.2.3<br />
-        Allow from 192.168.1.104 192.168.1.205
-      </example>
+      <highlight language="config">
+Allow from 10.1.2.3
+Allow from 192.168.1.104 192.168.1.205
+      </highlight>
       <p>An IP address of a host allowed access</p></dd>
 
       <dt>A partial IP address</dt>
 
       <dd>
-      <example><title>Example:</title>
-        Allow from 10.1<br />
-        Allow from 10 172.20 192.168.2
-      </example>
+      <highlight language="config">
+Allow from 10.1
+Allow from 10 172.20 192.168.2
+      </highlight>
       <p>The first 1 to 3 bytes of an IP address, for subnet
       restriction.</p></dd>
 
       <dt>A network/netmask pair</dt>
 
       <dd>
-      <example><title>Example:</title>
+      <highlight language="config">
         Allow from 10.1.0.0/255.255.0.0
-      </example>
+      </highlight>
       <p>A network a.b.c.d, and a netmask w.x.y.z. For more
       fine-grained subnet restriction.</p></dd>
 
       <dt>A network/nnn CIDR specification</dt>
 
       <dd>
-      <example><title>Example:</title>
+      <highlight language="config">
         Allow from 10.1.0.0/16
-      </example>
+      </highlight>
       <p>Similar to the previous case, except the netmask consists of
       nnn high-order 1 bits.</p></dd>
     </dl>
@@ -174,10 +174,10 @@ server</description>
     <p>IPv6 addresses and IPv6 subnets can be specified as shown
     below:</p>
 
-    <example>
-       Allow from 2001:db8::a00:20ff:fea7:ccea<br />
-       Allow from 2001:db8::a00:20ff:fea7:ccea/10
-    </example>
+    <highlight language="config">
+Allow from 2001:db8::a00:20ff:fea7:ccea
+Allow from 2001:db8::a00:20ff:fea7:ccea/10
+    </highlight>
 
     <p>The third format of the arguments to the
     <directive>Allow</directive> directive allows access to the server
@@ -196,16 +196,14 @@ server</description>
     <code>User-Agent</code> (browser type), <code>Referer</code>, or
     other HTTP request header fields.</p>
 
-    <example><title>Example:</title>
-      SetEnvIf User-Agent ^KnockKnock/2\.0 let_me_in<br />
-      &lt;Directory /docroot&gt;<br />
-      <indent>
-        Order Deny,Allow<br />
-        Deny from all<br />
-        Allow from env=let_me_in<br />
-      </indent>
-      &lt;/Directory&gt;
-    </example>
+    <highlight language="config">
+SetEnvIf User-Agent ^KnockKnock/2\.0 let_me_in
+&lt;Directory /docroot&gt;
+    Order Deny,Allow
+    Deny from all
+    Allow from env=let_me_in
+&lt;/Directory&gt;
+    </highlight>
 
     <p>In this case, browsers with a user-agent string beginning
     with <code>KnockKnock/2.0</code> will be allowed access, and all
@@ -341,11 +339,11 @@ evaluated.</description>
     <p>In the following example, all hosts in the example.org domain
     are allowed access; all other hosts are denied access.</p>
 
-    <example>
-      Order Deny,Allow<br />
-      Deny from all<br />
-      Allow from example.org
-    </example>
+    <highlight language="config">
+Order Deny,Allow
+Deny from all
+Allow from example.org
+    </highlight>
 
     <p>In the next example, all hosts in the example.org domain are
     allowed access, except for the hosts which are in the
@@ -354,11 +352,11 @@ evaluated.</description>
     state is to <directive module="mod_access_compat">Deny</directive>
     access to the server.</p>
 
-    <example>
-      Order Allow,Deny<br />
-      Allow from example.org<br />
-      Deny from foo.example.org
-    </example>
+    <highlight language="config">
+Order Allow,Deny
+Allow from example.org
+Deny from foo.example.org
+    </highlight>
 
     <p>On the other hand, if the <directive>Order</directive> in the
     last example is changed to <code>Deny,Allow</code>, all hosts will
@@ -377,13 +375,11 @@ evaluated.</description>
     directives because of its effect on the default access state. For
     example,</p>
 
-    <example>
-      &lt;Directory /www&gt;<br />
-      <indent>
-        Order Allow,Deny<br />
-      </indent>
-      &lt;/Directory&gt;
-    </example>
+    <highlight language="config">
+&lt;Directory /www&gt;
+    Order Allow,Deny
+&lt;/Directory&gt;
+    </highlight>
 
     <p>will Deny all access to the <code>/www</code> directory
     because the default access state is set to
@@ -448,27 +444,27 @@ later</compatibility>
     people outside of your network provide a password, you could use a
     configuration similar to the following:</p>
 
-    <example>
-      Require valid-user<br />
-      Allow from 192.168.1<br />
-      Satisfy Any
-    </example>
+    <highlight language="config">
+Require valid-user
+Allow from 192.168.1
+Satisfy Any
+    </highlight>
 
     <p>
     Another frequent use of the <directive>Satisfy</directive> directive
     is to relax access restrictions for a subdirectory:
     </p>
 
-    <example>
-      &lt;Directory /var/www/private&gt;<br />
-        Require valid-user<br />
-      &lt;/Directory&gt;<br />
-      <br />
-      &lt;Directory /var/www/private/public&gt;<br />
-        Allow from all<br />
-        Satisfy Any<br />
-      &lt;/Directory&gt;
-    </example>
+    <highlight language="config">
+&lt;Directory /var/www/private&gt;
+    Require valid-user
+&lt;/Directory&gt;
+
+&lt;Directory /var/www/private/public&gt;
+    Allow from all
+    Satisfy Any
+&lt;/Directory&gt;
+    </highlight>
 
     <p>In the above example, authentication will be required for the
     <code>/var/www/private</code> directory, but will not be required

Modified: httpd/httpd/branches/2.4.x/docs/manual/mod/mod_actions.xml
URL: http://svn.apache.org/viewvc/httpd/httpd/branches/2.4.x/docs/manual/mod/mod_actions.xml?rev=1334008&r1=1334007&r2=1334008&view=diff
==============================================================================
--- httpd/httpd/branches/2.4.x/docs/manual/mod/mod_actions.xml (original)
+++ httpd/httpd/branches/2.4.x/docs/manual/mod/mod_actions.xml Fri May  4 14:59:59 2012
@@ -74,21 +74,24 @@ introduced in Apache 2.1</compatibility>
     is passed using the <code>REDIRECT_HANDLER</code> variable.</p>
 
     <example><title>Example: MIME type</title>
-      # Requests for files of a particular MIME content type:<br />
-      Action image/gif /cgi-bin/images.cgi<br />
-      <br />
+    <highlight language="config">
+# Requests for files of a particular MIME content type:
+Action image/gif /cgi-bin/images.cgi
+    </highlight>
     </example>
 
     <p>In this example, requests for files with a MIME content
     type of <code>image/gif</code> will be handled by the
     specified cgi script <code>/cgi-bin/images.cgi</code>.</p>
 
-    <example><title>Example: File extension</title>
-      # Files of a particular file extension<br />
-      AddHandler my-file-type .xyz<br />
-      Action my-file-type /cgi-bin/program.cgi<br />
+    <example>
+        <title>Example: File extension</title>
+    <highlight language="config">
+# Files of a particular file extension
+AddHandler my-file-type .xyz
+Action my-file-type /cgi-bin/program.cgi
+    </highlight>
     </example>
-
     <p>In this example, requests for files with a file extension of
     <code>.xyz</code> are handled by the specified cgi script
     <code>/cgi-bin/program.cgi</code>.</p>
@@ -98,14 +101,12 @@ introduced in Apache 2.1</compatibility>
     if you want to use the <directive>Action</directive> directive in
     virtual locations.</p>
 
-    <example><title>Example</title>
-      &lt;Location /news&gt;<br />
-      <indent>
-        SetHandler news-handler<br />
-        Action news-handler /cgi-bin/news.cgi virtual<br />
-      </indent>
-      &lt;/Location&gt;
-    </example>
+    <highlight language="config">
+&lt;Location /news&gt;
+    SetHandler news-handler
+    Action news-handler /cgi-bin/news.cgi virtual
+&lt;/Location&gt;
+    </highlight>
 </usage>
 
 <seealso><directive module="mod_mime">AddHandler</directive></seealso>
@@ -145,13 +146,13 @@ method.</description>
     (<em>e.g.</em>, foo.html?hi). Otherwise, the request will
     proceed normally.</p>
 
-    <example><title>Examples</title>
-      # All GET requests go here<br />
-      Script GET /cgi-bin/search<br />
-      <br />
-      # A CGI PUT handler<br />
-      Script PUT /~bob/put.cgi<br />
-    </example>
+    <highlight language="config">
+# All GET requests go here
+Script GET /cgi-bin/search
+
+# A CGI PUT handler
+Script PUT /~bob/put.cgi
+    </highlight>
 </usage>
 </directivesynopsis>
 

Modified: httpd/httpd/branches/2.4.x/docs/manual/mod/mod_alias.xml
URL: http://svn.apache.org/viewvc/httpd/httpd/branches/2.4.x/docs/manual/mod/mod_alias.xml?rev=1334008&r1=1334007&r2=1334008&view=diff
==============================================================================
--- httpd/httpd/branches/2.4.x/docs/manual/mod/mod_alias.xml (original)
+++ httpd/httpd/branches/2.4.x/docs/manual/mod/mod_alias.xml Fri May  4 14:59:59 2012
@@ -79,10 +79,10 @@ href="../urlmapping.html">Mapping URLs t
     all the directives to have an effect.  For example, the following
     configuration will work as expected:</p>
 
-    <example>
-    Alias /foo/bar /baz<br />
-    Alias /foo /gaq
-    </example>
+    <highlight language="config">
+Alias /foo/bar /baz
+Alias /foo /gaq
+    </highlight>
 
     <p>But if the above two directives were reversed in order, the
     <code>/foo</code> <directive module="mod_alias">Alias</directive>
@@ -110,9 +110,9 @@ href="../urlmapping.html">Mapping URLs t
     <var>URL-path</var> is case-sensitive, even on case-insensitive
     file systems.</p>
 
-    <example><title>Example:</title>
+    <highlight language="config">
       Alias /image /ftp/pub/image
-    </example>
+    </highlight>
 
     <p>A request for <code>http://example.com/image/foo.gif</code> would cause
     the server to return the file <code>/ftp/pub/image/foo.gif</code>.  Only
@@ -146,14 +146,12 @@ href="../urlmapping.html">Mapping URLs t
     module="core">DocumentRoot</directive>, you may need to explicitly
     permit access to the target directory.</p>
 
-    <example><title>Example:</title>
-        Alias /image /ftp/pub/image<br />
-        &lt;Directory /ftp/pub/image&gt;<br />
-        <indent>
-            Require all granted<br />
-        </indent>
-        &lt;/Directory&gt;
-    </example>
+    <highlight language="config">
+Alias /image /ftp/pub/image
+&lt;Directory /ftp/pub/image&gt;
+    Require all granted
+&lt;/Directory&gt;
+    </highlight>
 
 </usage>
 </directivesynopsis>
@@ -178,18 +176,18 @@ expressions</description>
     example, to activate the <code>/icons</code> directory, one might
     use:</p>
 
-    <example>
+    <highlight language="config">
       AliasMatch ^/icons(.*) /usr/local/apache/icons$1
-    </example>
+    </highlight>
 
     <p>The full range of <glossary ref="regex">regular expression</glossary>
     power is available.  For example,
     it is possible to construct an alias with case-insensitive
     matching of the URL-path:</p>
 
-    <example>
+    <highlight language="config">
       AliasMatch (?i)^/image(.*) /ftp/pub/image$1
-    </example>
+    </highlight>
 
     <p>One subtle difference
     between <directive module="mod_alias">Alias</directive>
@@ -212,22 +210,22 @@ expressions</description>
 
     <p>For example, suppose you want to replace this with AliasMatch:</p>
 
-    <example>
+    <highlight language="config">
       Alias /image/ /ftp/pub/image/
-    </example>
+    </highlight>
 
     <p>This is NOT equivalent - don't do this!  This will send all
     requests that have /image/ anywhere in them to /ftp/pub/image/:</p>
 
-    <example>
+    <highlight language="config">
       AliasMatch /image/ /ftp/pub/image/
-    </example>
+    </highlight>
 
     <p>This is what you need to get the same effect:</p>
 
-    <example>
+    <highlight language="config">
       AliasMatch ^/image/(.*)$ /ftp/pub/image/$1
-    </example>
+    </highlight>
 
     <p>Of course, there's no point in
     using <directive module="mod_alias">AliasMatch</directive>
@@ -236,10 +234,10 @@ expressions</description>
     you do more complicated things.  For example, you could
     serve different kinds of files from different directories:</p>
 
-    <example>
+    <highlight language="config">
       AliasMatch ^/image/(.*)\.jpg$ /files/jpg.images/$1.jpg<br/>
       AliasMatch ^/image/(.*)\.gif$ /files/gif.images/$1.gif
-    </example>
+    </highlight>
 
 </usage>
 </directivesynopsis>
@@ -271,13 +269,13 @@ a different URL</description>
     <em>URL</em>.  Additional path information beyond the matched
     <em>URL-Path</em> will be appended to the target URL.</p>
 
-    <example><title>Example:</title>
-      # Redirect to a URL on a different host<br />
-      Redirect /service http://foo2.example.com/service<br />
-      <br />
-      # Redirect to a URL on the same host<br />
-      Redirect /one /two
-    </example>
+    <highlight language="config">
+# Redirect to a URL on a different host
+Redirect /service http://foo2.example.com/service
+
+# Redirect to a URL on the same host
+Redirect /one /two
+    </highlight>
 
     <p>If the client requests <code>http://example.com/service/foo.txt</code>,
     it will be told to access
@@ -335,10 +333,10 @@ a different URL</description>
     HTTP status code, known to the Apache HTTP Server (see the function
     <code>send_error_response</code> in http_protocol.c).</p>
 
-    <example><title>Example:</title>
-      Redirect permanent /one http://example.com/two<br />
-      Redirect 303 /three http://example.com/other
-    </example>
+    <highlight language="config">
+Redirect permanent /one http://example.com/two
+Redirect 303 /three http://example.com/other
+    </highlight>
 
 </usage>
 </directivesynopsis>
@@ -364,9 +362,9 @@ of the current URL</description>
     example, to redirect all GIF files to like-named JPEG files on
     another server, one might use:</p>
 
-    <example>
+    <highlight language="config">
       RedirectMatch (.*)\.gif$ http://other.example.com$1.jpg
-    </example>
+    </highlight>
 
     <p>The considerations related to the difference between
     <directive module="mod_alias">Alias</directive> and
@@ -432,29 +430,27 @@ target as a CGI script</description>
     to scripts beginning with the second argument, which is a full
     pathname in the local filesystem.</p>
 
-    <example><title>Example:</title>
+    <highlight language="config">
       ScriptAlias /cgi-bin/ /web/cgi-bin/
-    </example>
+    </highlight>
 
     <p>A request for <code>http://example.com/cgi-bin/foo</code> would cause the
     server to run the script <code>/web/cgi-bin/foo</code>.  This configuration
     is essentially equivalent to:</p>
-    <example>
-      Alias /cgi-bin/ /web/cgi-bin/<br />
-      &lt;Location /cgi-bin &gt;<br />
-      <indent>
-      SetHandler cgi-script<br />
-      Options +ExecCGI<br />
-      </indent>
-      &lt;/Location&gt;
-    </example>
+    <highlight language="config">
+Alias /cgi-bin/ /web/cgi-bin/
+&lt;Location /cgi-bin &gt;
+    SetHandler cgi-script
+    Options +ExecCGI
+&lt;/Location&gt;
+    </highlight>
 
 	<p><directive>ScriptAlias</directive> can also be used in conjunction with
 	a script or handler you have. For example:</p>
 
-	<example>
+	<highlight language="config">
 	  ScriptAlias /cgi-bin/ /web/cgi-handler.pl
-    </example>
+    </highlight>
 
     <p>In this scenario all files requested in <code>/cgi-bin/</code> will be
     handled by the file you have configured, this allows you to use your own custom
@@ -473,14 +469,12 @@ target as a CGI script</description>
     module="core" type="section">Directory</directive>, <directive
     module="core">SetHandler</directive>, and <directive
     module="core">Options</directive> as in:
-    <example>
-      &lt;Directory /usr/local/apache2/htdocs/cgi-bin &gt;<br />
-      <indent>
-      SetHandler cgi-script<br />
-      Options ExecCGI<br />
-      </indent>
-      &lt;/Directory&gt;
-    </example>
+    <highlight language="config">
+&lt;Directory /usr/local/apache2/htdocs/cgi-bin &gt;
+    SetHandler cgi-script
+    Options ExecCGI
+&lt;/Directory&gt;
+    </highlight>
     This is necessary since multiple <var>URL-paths</var> can map
     to the same filesystem location, potentially bypassing the
     <directive>ScriptAlias</directive> and revealing the source code
@@ -511,18 +505,18 @@ and designates the target as a CGI scrip
     example, to activate the standard <code>/cgi-bin</code>, one
     might use:</p>
 
-    <example>
+    <highlight language="config">
       ScriptAliasMatch ^/cgi-bin(.*) /usr/local/apache/cgi-bin$1
-    </example>
+    </highlight>
 
     <p>As for AliasMatch, the full range of <glossary ref="rexex">regular
     expression</glossary> power is available.
     For example, it is possible to construct an alias with case-insensitive
     matching of the URL-path:</p>
 
-    <example>
+    <highlight language="config">
       ScriptAliasMatch (?i)^/cgi-bin(.*) /usr/local/apache/cgi-bin$1
-    </example>
+    </highlight>
 
     <p>The considerations related to the difference between
     <directive module="mod_alias">Alias</directive> and

Modified: httpd/httpd/branches/2.4.x/docs/manual/mod/mod_allowmethods.xml
URL: http://svn.apache.org/viewvc/httpd/httpd/branches/2.4.x/docs/manual/mod/mod_allowmethods.xml?rev=1334008&r1=1334007&r2=1334008&view=diff
==============================================================================
--- httpd/httpd/branches/2.4.x/docs/manual/mod/mod_allowmethods.xml (original)
+++ httpd/httpd/branches/2.4.x/docs/manual/mod/mod_allowmethods.xml Fri May  4 14:59:59 2012
@@ -42,13 +42,11 @@ in order for it to rebuild correctly.
 <p>This module makes it easy to restrict what HTTP methods can
 used on an server. The most common configuration would be:</p>
 
-<example><title>Example</title>
-&lt;Location /&gt;<br />
-<indent>
-   AllowMethods GET POST OPTIONS<br />
-</indent>
+<highlight language="config">
+&lt;Location /&gt;
+   AllowMethods GET POST OPTIONS
 &lt;/Location&gt;
-</example>
+</highlight>
 
 </summary>
 
@@ -68,13 +66,11 @@ RFC given in upper case. The GET and HEA
 equivalent. The <code>reset</code> keyword can be used
 turn off <module>mod_allowmethods</module> in a deeper nested context:</p>
 
-<example><title>Example</title>
-&lt;Location /svn&gt;<br />
-<indent>
-   AllowMethods reset<br />
-</indent>
+<highlight language="config">
+&lt;Location /svn&gt;
+   AllowMethods reset
 &lt;/Location&gt;
-</example>
+</highlight>
 
 <note><title>Caution</title>
   <p>The TRACE method can not be denied by this module,

Modified: httpd/httpd/branches/2.4.x/docs/manual/mod/mod_asis.xml
URL: http://svn.apache.org/viewvc/httpd/httpd/branches/2.4.x/docs/manual/mod/mod_asis.xml?rev=1334008&r1=1334007&r2=1334008&view=diff
==============================================================================
--- httpd/httpd/branches/2.4.x/docs/manual/mod/mod_asis.xml (original)
+++ httpd/httpd/branches/2.4.x/docs/manual/mod/mod_asis.xml Fri May  4 14:59:59 2012
@@ -51,7 +51,7 @@ HTTP headers</description>
     <p>In the server configuration file, associate files with the
     <code>send-as-is</code> handler <em>e.g.</em></p>
 
-    <example>AddHandler send-as-is asis</example>
+    <highlight language="config">AddHandler send-as-is asis</highlight>
 
     <p>The contents of any file with a <code>.asis</code> extension
     will then be sent by Apache httpd to the client with almost no

Modified: httpd/httpd/branches/2.4.x/docs/manual/mod/mod_auth_basic.xml
URL: http://svn.apache.org/viewvc/httpd/httpd/branches/2.4.x/docs/manual/mod/mod_auth_basic.xml?rev=1334008&r1=1334007&r2=1334008&view=diff
==============================================================================
--- httpd/httpd/branches/2.4.x/docs/manual/mod/mod_auth_basic.xml (original)
+++ httpd/httpd/branches/2.4.x/docs/manual/mod/mod_auth_basic.xml Fri May  4 14:59:59 2012
@@ -59,20 +59,18 @@
     The default <code>file</code> provider is implemented
     by the <module>mod_authn_file</module> module.  Make sure
     that the chosen provider module is present in the server.</p>
-
     <example><title>Example</title>
-      &lt;Location /secure&gt;<br />
-      <indent>
-        AuthType basic<br />
-        AuthName "private area"<br />
-        AuthBasicProvider  dbm<br />
-        AuthDBMType        SDBM<br />
-        AuthDBMUserFile    /www/etc/dbmpasswd<br />
-        Require            valid-user<br />
-      </indent>
-      &lt;/Location&gt;
+    <highlight language="config">
+&lt;Location /secure&gt;
+    AuthType basic
+    AuthName "private area"
+    AuthBasicProvider  dbm
+    AuthDBMType        SDBM
+    AuthDBMUserFile    /www/etc/dbmpasswd
+    Require            valid-user
+&lt;/Location&gt;
+    </highlight>
     </example>
-
     <p> Providers are queried in order until a provider finds a match
     for the requested username, at which point this sole provider will
     attempt to check the password.  A failure to verify the password does

Modified: httpd/httpd/branches/2.4.x/docs/manual/mod/mod_auth_digest.xml
URL: http://svn.apache.org/viewvc/httpd/httpd/branches/2.4.x/docs/manual/mod/mod_auth_digest.xml?rev=1334008&r1=1334007&r2=1334008&view=diff
==============================================================================
--- httpd/httpd/branches/2.4.x/docs/manual/mod/mod_auth_digest.xml (original)
+++ httpd/httpd/branches/2.4.x/docs/manual/mod/mod_auth_digest.xml Fri May  4 14:59:59 2012
@@ -56,17 +56,17 @@
     <program>htdigest</program> tool.</p>
 
     <example><title>Example:</title>
-      &lt;Location /private/&gt;<br />
-      <indent>
-        AuthType Digest<br />
-        AuthName "private area"<br />
-        AuthDigestDomain /private/ http://mirror.my.dom/private2/<br />
-        <br />
-        AuthDigestProvider file<br />
-        AuthUserFile /web/auth/.digest_pw<br />
-        Require valid-user<br />
-      </indent>
-      &lt;/Location&gt;
+    <highlight language="config">
+&lt;Location /private/&gt;
+    AuthType Digest
+    AuthName "private area"
+    AuthDigestDomain /private/ http://mirror.my.dom/private2/
+    
+    AuthDigestProvider file
+    AuthUserFile /web/auth/.digest_pw
+    Require valid-user
+&lt;/Location&gt;
+      </highlight>
     </example>
 
     <note><title>Note</title>
@@ -113,7 +113,9 @@
     method would look similar to the following.</p>
 
     <example><title>Using Digest Authentication with MSIE:</title>
-    BrowserMatch "MSIE" AuthDigestEnableQueryStringHack=On
+    <highlight language="config">
+        BrowserMatch "MSIE" AuthDigestEnableQueryStringHack=On
+    </highlight>
     </example>
 
     <p>This workaround is not necessary for MSIE 7, though enabling it does
@@ -335,11 +337,11 @@ of clients</description>
     express your value as KBytes or MBytes. For example, the following
     directives are all equivalent:</p>
 
-    <example>
-      AuthDigestShmemSize 1048576<br />
-      AuthDigestShmemSize 1024K<br />
-      AuthDigestShmemSize 1M
-    </example>
+<highlight language="config">
+AuthDigestShmemSize 1048576
+AuthDigestShmemSize 1024K
+AuthDigestShmemSize 1M
+    </highlight>
 </usage>
 </directivesynopsis>
 

Modified: httpd/httpd/branches/2.4.x/docs/manual/mod/mod_auth_form.xml
URL: http://svn.apache.org/viewvc/httpd/httpd/branches/2.4.x/docs/manual/mod/mod_auth_form.xml?rev=1334008&r1=1334007&r2=1334008&view=diff
==============================================================================
--- httpd/httpd/branches/2.4.x/docs/manual/mod/mod_auth_form.xml (original)
+++ httpd/httpd/branches/2.4.x/docs/manual/mod/mod_auth_form.xml Fri May  4 14:59:59 2012
@@ -74,14 +74,16 @@
       the user will be redirected to the form login page.</p>
 
       <example><title>Basic example</title>
-        AuthFormProvider file<br />
-        AuthUserFile conf/passwd<br />
-        AuthType form<br />
-        AuthName realm<br />
-        AuthFormLoginRequiredLocation http://example.com/login.html<br />
-        Session On<br />
-        SessionCookieName session path=/<br />
-        SessionCryptoPassphrase secret<br />
+      <highlight language="config">
+AuthFormProvider file
+AuthUserFile conf/passwd
+AuthType form
+AuthName realm
+AuthFormLoginRequiredLocation http://example.com/login.html
+Session On
+SessionCookieName session path=/
+SessionCryptoPassphrase secret
+        </highlight>
       </example>
 
       <p>The directive <directive module="mod_authn_core">AuthType</directive> will enable
@@ -128,20 +130,20 @@
       Apache httpd as follows:</p>
 
       <example><title>Form login handler example</title>
-        &lt;Location /dologin.html&gt;
-        <indent>
-          SetHandler form-login-handler<br />
-          AuthFormLoginRequiredLocation http://example.com/login.html<br />
-          AuthFormLoginSuccessLocation http://example.com/success.html<br />
-          AuthFormProvider file<br />
-          AuthUserFile conf/passwd<br />
-          AuthType form<br />
-          AuthName realm<br />
-          Session On<br />
-          SessionCookieName session path=/<br />
-          SessionCryptoPassphrase secret<br />
-        </indent>
-        &lt;/Location&gt;
+      <highlight language="config">
+&lt;Location /dologin.html&gt;
+    SetHandler form-login-handler
+    AuthFormLoginRequiredLocation http://example.com/login.html
+    AuthFormLoginSuccessLocation http://example.com/success.html
+    AuthFormProvider file
+    AuthUserFile conf/passwd
+    AuthType form
+    AuthName realm
+    Session On
+    SessionCookieName session path=/
+    SessionCryptoPassphrase secret
+&lt;/Location&gt;
+        </highlight>
       </example>
 
       <p>The URLs specified by the
@@ -195,15 +197,17 @@
       containing the login form, as follows:</p>
 
       <example><title>Basic inline example</title>
-        AuthFormProvider file<br />
-        <strong>ErrorDocument 401 /login.shtml</strong><br />
-        AuthUserFile conf/passwd<br />
-        AuthType form<br />
-        AuthName realm<br />
-        AuthFormLoginRequiredLocation http://example.com/login.html<br />
-        Session On<br />
-        SessionCookieName session path=/<br />
-        SessionCryptoPassphrase secret<br />
+      <highlight language="config">
+AuthFormProvider file
+ErrorDocument 401 /login.shtml
+AuthUserFile conf/passwd
+AuthType form
+AuthName realm
+AuthFormLoginRequiredLocation http://example.com/login.html
+Session On
+SessionCookieName session path=/
+SessionCryptoPassphrase secret
+        </highlight>
       </example>
 
       <p>The error document page should contain a login form with an empty action property,
@@ -272,9 +276,11 @@
       technology.</p>
 
       <example><title>CGI example</title>
-        AuthFormProvider file<br />
-        <strong>ErrorDocument 401 /cgi-bin/login.cgi</strong><br />
-        ...<br />
+      <highlight language="config">
+        AuthFormProvider file
+        <strong>ErrorDocument 401 /cgi-bin/login.cgi</strong>
+        ...
+        </highlight>
       </example>
 
     </section>
@@ -293,12 +299,14 @@
       give the user the option to log in again.</p>
 
       <example><title>Basic logout example</title>
-        SetHandler form-logout-handler<br />
-        AuthName realm<br />
-        AuthFormLogoutLocation http://example.com/loggedout.html<br />
-        Session On<br />
-        SessionCookieName session path=/<br />
-        SessionCryptoPassphrase secret<br />
+      <highlight language="config">
+SetHandler form-logout-handler
+AuthName realm
+AuthFormLogoutLocation http://example.com/loggedout.html
+Session On
+SessionCookieName session path=/
+SessionCryptoPassphrase secret
+        </highlight>
       </example>
 
       <p>Note that logging a user out does not delete the session; it merely removes
@@ -310,12 +318,14 @@
       </p>
 
       <example><title>Basic session expiry example</title>
-        SetHandler form-logout-handler<br />
-        AuthFormLogoutLocation http://example.com/loggedout.html<br />
-        Session On<br />
-        SessionMaxAge 1<br />
-        SessionCookieName session path=/<br />
-        SessionCryptoPassphrase secret<br />
+      <highlight language="config">
+SetHandler form-logout-handler
+AuthFormLogoutLocation http://example.com/loggedout.html
+Session On
+SessionMaxAge 1
+SessionCookieName session path=/
+SessionCryptoPassphrase secret
+        </highlight>
       </example>
 
     </section>
@@ -345,17 +355,17 @@
     that the chosen provider module is present in the server.</p>
 
     <example><title>Example</title>
-      &lt;Location /secure&gt;<br />
-      <indent>
-        AuthType form<br />
-        AuthName "private area"<br />
-        AuthFormProvider  dbm<br />
-        AuthDBMType        SDBM<br />
-        AuthDBMUserFile    /www/etc/dbmpasswd<br />
-        Require            valid-user<br />
-        ...<br />
-      </indent>
-      &lt;/Location&gt;
+    <highlight language="config">
+&lt;Location /secure&gt;
+    AuthType form
+    AuthName "private area"
+    AuthFormProvider  dbm
+    AuthDBMType        SDBM
+    AuthDBMUserFile    /www/etc/dbmpasswd
+    Require            valid-user
+    #...
+&lt;/Location&gt;
+      </highlight>
     </example>
 
     <p>Providers are implemented by <module>mod_authn_dbm</module>,
@@ -614,14 +624,14 @@ lower level modules</description>
     the page specified by this directive will be shown to the end user. For example:</p>
 
     <example><title>Example</title>
-      &lt;Location /logout&gt;<br />
-      <indent>
-        SetHandler form-logout-handler<br />
-        AuthFormLogoutLocation http://example.com/loggedout.html<br />
-        Session on<br />
-        ...
-      </indent>
-      &lt;/Location&gt;
+    <highlight language="config">
+&lt;Location /logout&gt;
+    SetHandler form-logout-handler
+    AuthFormLogoutLocation http://example.com/loggedout.html
+    Session on
+    #...
+&lt;/Location&gt;
+      </highlight>
     </example>
 
     <p>An attempt to access the URI <var>/logout/</var> will result in the user being logged

Modified: httpd/httpd/branches/2.4.x/docs/manual/mod/mod_authn_anon.xml
URL: http://svn.apache.org/viewvc/httpd/httpd/branches/2.4.x/docs/manual/mod/mod_authn_anon.xml?rev=1334008&r1=1334007&r2=1334008&view=diff
==============================================================================
--- httpd/httpd/branches/2.4.x/docs/manual/mod/mod_authn_anon.xml (original)
+++ httpd/httpd/branches/2.4.x/docs/manual/mod/mod_authn_anon.xml Fri May  4 14:59:59 2012
@@ -81,24 +81,22 @@
     </ul>
 
     <example><title>Example</title>
-      &lt;Directory /var/www/html/private&gt;
-      <indent>
-        AuthName "Use 'anonymous' &amp; Email address for guest entry"<br />
-        AuthType Basic<br />
-        AuthBasicProvider file anon<br />
-        AuthUserFile /path/to/your/.htpasswd<br />
-        <br />
-        Anonymous_NoUserID off<br />
-        Anonymous_MustGiveEmail on<br />
-        Anonymous_VerifyEmail on<br />
-        Anonymous_LogEmail on<br />
-        Anonymous anonymous guest www test welcome<br />
-        <br />
-        Require all granted<br />
-        <br />
-        Require valid-user<br />
-      </indent>
-      &lt;/Directory&gt;
+    <highlight language="config">
+&lt;Directory /var/www/html/private&gt;
+    AuthName "Use 'anonymous' &amp; Email address for guest entry"
+    AuthType Basic
+    AuthBasicProvider file anon
+    AuthUserFile /path/to/your/.htpasswd
+    
+    Anonymous_NoUserID off
+    Anonymous_MustGiveEmail on
+    Anonymous_VerifyEmail on
+    Anonymous_LogEmail on
+    Anonymous anonymous guest www test welcome
+    
+    Require valid-user
+&lt;/Directory&gt;
+      </highlight>
     </example>
 </section>
 
@@ -124,7 +122,9 @@ password verification</description>
     userIDs.</p>
 
     <example><title>Example:</title>
+    <highlight language="config">
       Anonymous anonymous "Not Registered" "I don't know"
+    </highlight>
     </example>
 
     <p>This would allow the user to enter without password



Mime
View raw message