<usage>
<p>When set, this directive limits the action of the spelling correction
- to lower/upper case changes.
- Other potential corrections are not performed.</p>
-
+ to lower/upper case changes. Other potential corrections are not performed,
+ except when <directive>CheckBasenameMatch</directive> is also set.</p>
</usage>
</directivesynopsis>
<directivesynopsis>
<name>CheckBasenameMatch</name>
-<description>Extend the action of the speling module to also check filename
-without paying attention to the extention. (e.g. foo.gif and foo.jpg).
-This can be particulary useful in conjunction with
-<a href="../content-negotiation.html">MultiViews</a></description>
+<description>Also match files with differing file name extensions.</description>
<syntax>CheckBasenameMatch on|off</syntax>
<default>CheckBasenameMatch Off</default>
<contextlist>
<override>Options</override>
<usage>
- <p>This option has no effect if <directive>CheckCaseOnly</directive> is set.</p>
-
+ <p>When set, this directive extends the action of the spelling correction
+ to the file name extension. For example a file <code>foo.gif</code> will
+ match a request for <code>foo</code> or <code>foo.jpg</code>. This can be
+ particulary useful in conjunction with
+ <a href="../content-negotiation.html">MultiViews</a>.</p>
</usage>
</directivesynopsis>
* because it won't find anything matching that spelling.
* With the extension-munging, it would locate "foobar.html".
*/
- else if ((cfg->check_case_only == 0) &&
- (cfg->check_basename_match == 1)) {
+ else if (cfg->check_basename_match == 1) {
/*
* Okay... we didn't find anything. Now we take out the hard-core
* power tools. There are several cases here. Someone might have