element (such as cutting off the end of a bolded phrase), the
results may affect the rest of the directory listing.</p>
</div>
+ <div class="note"><h3>Compatibility</h3>
+ <p> Prior to version 2.4, any wild-card expression that contained slashes
+ was treated as if it started with a '*'.</p>
+ </div>
</div>
<div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
element (such as cutting off the end of a bolded phrase), the
results may affect the rest of the directory listing.</p>
</note>
+ <note><title>Compatibility</title>
+ <p> Prior to version 2.4, any wild-card expression that contained slashes
+ was treated as if it started with a '*'.</p>
+ </note>
</usage>
</directivesynopsis>
display descriptions for .xhtml files, which were previously
ignored.</li>
+ <li><code class="module"><a href="./mod/mod_autoindex.html">mod_autoindex</a></code>: AddDescription 'file' arguments
+ that contain wild-cards and slashes are no longer implicitly treated
+ as if they began with a '*' character.</li>
+
<li><code class="module"><a href="./mod/mod_ssl.html">mod_ssl</a></code>: The default format of the <code>*_DN</code>
variables has changed. The old format can still be used with the new
<code>LegacyDNStringFormat</code> argument to <code class="directive"><a href="./mod/mod_ssl.html#ssloptions">SSLOptions</a></code>. The SSLv2 protocol is
display descriptions for .xhtml files, which were previously
ignored.</li>
+ <li><module>mod_autoindex</module>: AddDescription 'file' arguments
+ that contain wild-cards and slashes are no longer implicitly treated
+ as if they began with a '*' character.</li>
+
<li><module>mod_ssl</module>: The default format of the <code>*_DN</code>
variables has changed. The old format can still be used with the new
<code>LegacyDNStringFormat</code> argument to <directive