<a href="mod/mod_access.html">mod_access</a><br>
<a href="mod/mod_cgi.html">mod_cgi</a><br>
+<a href="mod/mod_headers.html">mod_headers</a><br>
<a href="mod/mod_include.html">mod_include</a><br>
<a href="mod/mod_log_config.html">mod_log_config</a><br>
<a href="mod/mod_rewrite.html">mod_rewrite</a><br>
<A HREF="mod/mod_access.html#allow">Allow</A><br>
<a href="mod/mod_log_config.html#customlog">CustomLog</a><br>
<A HREF="mod/mod_access.html#deny">Deny</A><br>
+<a href="mod/mod_headers.html#Header">Header</a><br>
<a href="mod/mod_log_config.html#logformat">LogFormat</a><br>
<A HREF="mod/mod_rewrite.html#RewriteCond">RewriteCond</A><br>
<A HREF="mod/mod_rewrite.html#RewriteRule">RewriteRule</A><br>
log requests from clients which are outside your subnet.
</p>
+<h3>Conditional Response Headers</h3>
+
+<p>The <code>Header</code> directive can use the presence or absence
+of an environment variable to determine whether or not a certain
+HTTP header will be placed in the response to the client.
+This allows, for example, a certain response header to be sent
+only if a corresponding header is received in the request from
+the client.</p>
+
<h3>URL Rewriting</h3>
<p>The <code>%{ENV:...}</code> form of <em>TestString</em> in the
<a href="mod/mod_access.html">mod_access</a><br>
<a href="mod/mod_cgi.html">mod_cgi</a><br>
+<a href="mod/mod_headers.html">mod_headers</a><br>
<a href="mod/mod_include.html">mod_include</a><br>
<a href="mod/mod_log_config.html">mod_log_config</a><br>
<a href="mod/mod_rewrite.html">mod_rewrite</a><br>
<A HREF="mod/mod_access.html#allow">Allow</A><br>
<a href="mod/mod_log_config.html#customlog">CustomLog</a><br>
<A HREF="mod/mod_access.html#deny">Deny</A><br>
+<a href="mod/mod_headers.html#Header">Header</a><br>
<a href="mod/mod_log_config.html#logformat">LogFormat</a><br>
<A HREF="mod/mod_rewrite.html#RewriteCond">RewriteCond</A><br>
<A HREF="mod/mod_rewrite.html#RewriteRule">RewriteRule</A><br>
log requests from clients which are outside your subnet.
</p>
+<h3>Conditional Response Headers</h3>
+
+<p>The <code>Header</code> directive can use the presence or absence
+of an environment variable to determine whether or not a certain
+HTTP header will be placed in the response to the client.
+This allows, for example, a certain response header to be sent
+only if a corresponding header is received in the request from
+the client.</p>
+
<h3>URL Rewriting</h3>
<p>The <code>%{ENV:...}</code> form of <em>TestString</em> in the
<dd>New module in Apache 2.0. This module includes the functionality
of mod_mmap_static in Apache 1.3, plus adds further caching abilities.
+<dt><strong>mod_headers</strong>
+<dd>This module is much more flexible in Apache 2.0. It can now
+modify request headers used by mod_proxy, and it can conditionally set
+response headers.
+
</dl>
<!--#include virtual="footer.html" -->
<dd>New module in Apache 2.0. This module includes the functionality
of mod_mmap_static in Apache 1.3, plus adds further caching abilities.
+<dt><strong>mod_headers</strong>
+<dd>This module is much more flexible in Apache 2.0. It can now
+modify request headers used by mod_proxy, and it can conditionally set
+response headers.
+
</dl>
<!--#include virtual="footer.html" -->