directive now takes the argument <code>on</code> or
<code>off</code>. Existing instances of <code class="directive">CacheNegotiatedDocs</code> should be
replaced with <code>CacheNegotiatedDocs on</code>.</li>
<li>
The <code class="directive"><a href="./mod/core.html#errordocument">ErrorDocument</a></code>
directive no longer uses a quote at the beginning of the
argument to indicate a text message. Instead, you should
enclose the message in double quotes. For example, existing
instances of
<div class="example"><p><code>
ErrorDocument 403 "Some Message
</code></p></div>
should be replaced with
<div class="example"><p><code>
ErrorDocument 403 "Some Message"
</code></p></div>
As long as the second argument is not a valid URL or
pathname, it will be treated as a text message.
</li>
<li>The <code>AccessConfig</code> and
<code>ResourceConfig</code> directives no longer exist.
Existing instances of these directives can be replaced with
the <code class="directive"><a href="./mod/core.html#include">Include</a></code>
directive which has equivalent functionality. If you were
making use of the default values of these directives without
including them in the configuration files, you may need to
add <code>Include conf/access.conf</code> and <code>Include
conf/srm.conf</code> to your <code>httpd.conf</code>. In order to
assure that Apache reads the configuration files in the same order
as was implied by the older directives, the <code class="directive"><a href="./mod/core.html#include">Include</a></code> directives should be placed at the end
of <code>httpd.conf</code>, with the one for <code>srm.conf</code>
preceding the one for <code>access.conf</code>.</li>
<li>The <code>BindAddress</code> and <code>Port</code>
directives no longer exist. Equivalent functionality is
directive of <code class="module"><a href="./mod/mod_log_config.html">mod_log_config</a></code>.</li>
<li>The <code>AddModule</code> and
<code>ClearModuleList</code> directives no longer exist.
These directives were used to ensure that modules could be
enabled in the correct order. The new Apache 2.0 API allows
modules to explicitly specify their ordering, eliminating the
need for these directives.</li>
<li>The <code>FancyIndexing</code> directive has been removed.
The same functionality is available through the
<code>FancyIndexing</code> option to the <code class="directive"><a href="./mod/mod_autoindex.html#indexoptions">IndexOptions</a></code>
directive.</li>
<li>The MultiViews content-negotiation technique provided by
<code class="module"><a href="./mod/mod_negotiation.html">mod_negotiation</a></code> has become more strict in its
default file matching. It will select only from <em>negotiable</em>
files. The old behavior can be restored using the <code class="directive"><a href="./mod/mod_mime.html#multiviewsmatch">MultiviewsMatch</a></code> directive.</li>
