href="../sections.html#mergin">configuration sections</a>. These
two directives have a different effect if reversed:</p>
- <example>
- RequestHeader append MirrorID "mirror 12"<br />
- RequestHeader unset MirrorID
- </example>
+ <highlight language="config">
+RequestHeader append MirrorID "mirror 12"
+RequestHeader unset MirrorID
+ </highlight>
<p>This way round, the <code>MirrorID</code> header is not set. If
reversed, the MirrorID header is set to "mirror 12".</p>
Copy all request headers that begin with "TS" to the
response headers:
- <example>
+ <highlight language="config">
Header echo ^TS
- </example>
+ </highlight>
</li>
<li>
the client to intuit load on the server or in isolating
bottlenecks between the client and the server.
- <example>
+ <highlight language="config">
Header set MyHeader "%D %t"
- </example>
+ </highlight>
<p>results in this header being added to the response:</p>
<li>
Say hello to Joe
- <example>
- Header set MyHeader "Hello Joe. It took %D microseconds \<br />
- for Apache to serve this request."
- </example>
+ <highlight language="config">
+Header set MyHeader "Hello Joe. It took %D microseconds for Apache to serve this request."
+ </highlight>
<p>results in this header being added to the response:</p>
stimulus. Note that this example requires the services of the
<module>mod_setenvif</module> module.
- <example>
- SetEnvIf MyRequestHeader myvalue HAVE_MyRequestHeader<br />
- Header set MyHeader "%D %t mytext" env=HAVE_MyRequestHeader
- </example>
+ <highlight language="config">
+SetEnvIf MyRequestHeader myvalue HAVE_MyRequestHeader
+Header set MyHeader "%D %t mytext" env=HAVE_MyRequestHeader
+ </highlight>
<p>If the header <code>MyRequestHeader: myvalue</code> is present on
the HTTP request, the response will contain the following header:</p>
description</a>) by replacing <var>https:</var> with
<var>http:</var> in the <var>Destination</var> header:
- <example>
+ <highlight language="config">
RequestHeader edit Destination ^https: http: early
- </example>
+ </highlight>
</li>
<li>
<code>NO_STORE</code> environment variables all existed for the
request):
- <example>
- Header merge Cache-Control no-cache env=CGI<br />
- Header merge Cache-Control no-cache env=NO_CACHE<br />
- Header merge Cache-Control no-store env=NO_STORE
- </example>
+ <highlight language="config">
+Header merge Cache-Control no-cache env=CGI
+Header merge Cache-Control no-cache env=NO_CACHE
+Header merge Cache-Control no-store env=NO_STORE
+ </highlight>
<p>then the response would contain the following header:</p>
</li>
<li>
Set a test cookie if and only if the client didn't send us a cookie
- <example>
+ <highlight language="config">
Header set Set-Cookie testcookie "expr=-z %{req:Cookie}"
- </example>
+ </highlight>
</li>
</ol>
</section>
status information. This address will usually correspond to a configured
<directive module="mod_heartmonitor">HeartbeatListen</directive> on a
frontend proxy system.</p>
-<example>
+<highlight language="config">
HeartbeatAddress 239.0.0.1:27999
-</example>
+</highlight>
</usage>
</directivesynopsis>
module="mod_heartbeat">HeartbeatAddress</directive> on an origin server.
</p>
- <example>
+ <highlight language="config">
HeartbeatListen 239.0.0.1:27999
- </example>
+ </highlight>
<p> This module is inactive until this directive is used.</p>
</usage>
<p>The following directive will activate files ending with
<code>.map</code> as imagemap files:</p>
- <example>AddHandler imap-file map</example>
+ <highlight language="config">AddHandler imap-file map</highlight>
<p>Note that the following is still supported:</p>
- <example>AddType application/x-httpd-imap map</example>
+ <highlight language="config">AddType application/x-httpd-imap map</highlight>
<p>However, we are trying to phase out "magic MIME types" so we
are deprecating this method.</p>
parse them and assign the resulting document the mime type of
<code>text/html</code>:</p>
- <example>
- AddType text/html .shtml<br />
- AddOutputFilter INCLUDES .shtml
- </example>
+ <highlight language="config">
+AddType text/html .shtml
+AddOutputFilter INCLUDES .shtml
+ </highlight>
<p>The following directive must be given for the directories
containing the shtml files (typically in a
<directive module="core">AllowOverride</directive> <code>Options</code>
is set):</p>
- <example>
+ <highlight language="config">
Options +Includes
- </example>
+ </highlight>
<p>For backwards compatibility, the <code>server-parsed</code>
<a href="../handler.html">handler</a> also activates the
<p>This directive changes the string that <module>mod_include</module>
looks for to mark the end of an include element.</p>
- <example><title>Example</title>
+ <highlight language="config">
SSIEndTag "%>"
- </example>
+ </highlight>
</usage>
<seealso><directive module="mod_include">SSIStartTag</directive></seealso>
<p>This directive changes the string that <module>mod_include</module>
displays when a variable is not set and "echoed".</p>
- <example><title>Example</title>
+ <highlight language="config">
SSIUndefinedEcho "<!-- undef -->"
- </example>
+ </highlight>
</usage>
</directivesynopsis>
<p>This directive has the same effect as the <code><!--#config
errmsg=<var>message</var> --></code> element.</p>
- <example><title>Example</title>
+ <highlight language="config">
SSIErrorMsg "<!-- Error -->"
- </example>
+ </highlight>
</usage>
</directivesynopsis>
output of a file each processing different commands (possibly at
different times).</p>
- <example><title>Example</title>
+ <highlight language="config">
SSIStartTag "<%"<br />
SSIEndTag "%>"
- </example>
+ </highlight>
<p>The example given above, which also specifies a matching
<directive module="mod_include">SSIEndTag</directive>, will
<p>This directive has the same effect as the <code><!--#config
timefmt=<var>formatstring</var> --></code> element.</p>
- <example><title>Example</title>
+ <highlight language="config">
SSITimeFormat "%R, %B %d, %Y"
- </example>
+ </highlight>
<p>The above directive would cause times to be displayed in the
format "22:26, June 14, 2002".</p>
<p>To configure <module>mod_info</module>, add the following to your
<code>httpd.conf</code> file.</p>
- <example>
- <Location /server-info><br />
- <indent>
- SetHandler server-info<br />
- </indent>
- </Location>
- </example>
+ <highlight language="config">
+<Location /server-info>
+ SetHandler server-info
+</Location>
+ </highlight>
<p>You may wish to use <module>mod_access</module> inside the
<directive type="section" module="core">Location</directive>
directive to limit access to your server configuration
information:</p>
- <example>
- <Location /server-info><br />
- <indent>
- SetHandler server-info<br />
- Require host example.com<br />
- </indent>
- </Location>
- </example>
+ <highlight language="config">
+<Location /server-info>
+ SetHandler server-info
+ Require host example.com
+</Location>
+ </highlight>
<p>Once configured, the server information is obtained by
accessing <code>http://your.host.example.com/server-info</code></p>
to limit access to your server configuration information.</p>
<example><title>Access control</title>
- <Location /server-info><br />
- <indent>
- SetHandler server-info<br />
- Order allow,deny<br />
- # Allow access from server itself<br />
- Allow from 127.0.0.1<br />
- # Additionally, allow access from local workstation<br />
- Allow from 192.168.1.17<br />
- </indent>
- </Location>
+ <highlight language="config">
+<Location /server-info>
+ SetHandler server-info
+ Order allow,deny
+ # Allow access from server itself
+ Allow from 127.0.0.1
+ # Additionally, allow access from local workstation
+ Allow from 192.168.1.17
+</Location>
+ </highlight>
</example>
</section>
HTML interpreted, <strong>Additional Information</strong> for
the module <var>module-name</var>. Example:</p>
- <example>
- AddModuleInfo mod_deflate.c 'See <a \<br />
- <indent>
- href="http://www.apache.org/docs/&httpd.docs;/mod/mod_deflate.html">\<br />
- http://www.apache.org/docs/&httpd.docs;/mod/mod_deflate.html</a>'
- </indent>
- </example>
+ <highlight language="config">
+AddModuleInfo mod_deflate.c 'See <a \
+ href="http://www.apache.org/docs/&httpd.docs;/mod/mod_deflate.html">\
+ http://www.apache.org/docs/&httpd.docs;/mod/mod_deflate.html</a>'
+ </highlight>
</usage>
</directivesynopsis>
it to them with their file extensions. To enable any .dll file to be
processed as an ISAPI extension, edit the httpd.conf file and add the
following line:</p>
- <example>
+ <highlight language="config">
AddHandler isapi-handler .dll
- </example>
+ </highlight>
<note>In older versions of the Apache server,
<code>isapi-isa</code> was the proper handler name, rather than
requested module loaded. However, you may preload and keep a
specific module loaded by using the following syntax in your
httpd.conf:</p>
- <example>
+ <highlight language="config">
ISAPICacheFile c:/WebWork/Scripts/ISAPI/mytest.dll
- </example>
+ </highlight>
<p>Whether or not you have preloaded an ISAPI extension, all
ISAPI extensions are governed by the same permissions and
projects / apache / commitdiff