In the configuration file, e.g., httpd.conf, if you have:

DirectoryIndex index.html index.txt
DirectoryIndex disabled

Then, all the previous index files (index.html, index.txt in this case) are not disabled. This violates the semantics of the DirectoryIndex directive.

If the two DirectoryIndex directives are seperated in a large httpd.conf (e.g., a lot of other directives are in between), this will bring confusion to users.

Looking at the code in modules/mappers/mod_dir.c (see below), you can find that
the previous list is not cleared when an alone "disabled" is encountered.


    while ((w = ap_getword_conf(cmd->pool, &t)) && w[0]) {
        if (count == 0 && !strcasecmp(w, "disabled")) {
            /* peek to see if "disabled" is first in a series of arguments */
            const char *tt = t;
            const char *ww = ap_getword_conf(cmd->temp_pool, &tt);
            if (ww == NULL || !ww[0]) {
               /* "disabled" is first, and alone */
               break;
            }
        }
        *(const char **)apr_array_push(d->index_names) = w;
        count++;
    }