mod_autoindex/5087: HeaderName & ReadmeName require filename extension, even if file does not have an extension

[Jim Simmons <s4...@ornl.gov>]

>Number:         5087
>Category:       mod_autoindex
>Synopsis:       HeaderName & ReadmeName require filename extension, even if file does not have an extension
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    apache
>State:          open
>Class:          sw-bug
>Submitter-Id:   apache
>Arrival-Date:   Thu Sep 30 11:20:01 PDT 1999
>Last-Modified:
>Originator:     s4i@ornl.gov
>Organization:
apache
>Release:        1.3.9
>Environment:
Solaris 2.6, gcc 2.8.0
>Description:
Note: this has been reported elsewhere in other bug reports but I consider
this specific situation to be a big enough problem that it forces a return
to 1.3.6.

Basically, filenames listed in HeaderName directives have to have an extension
or they will not work.  In our case, we have README and HEADER files that
are named exactly README and HEADER.  It seems to be impossible to get
mod_autoindex to display these files anymore without renaming all of them
to include an extension.  This will mean changes to other links and
previously published documentation, which may not be acceptable.

This fails despite a "DefaultType text/plain" elsewhere in the configuration.
>How-To-Repeat:
Use a "HeaderName HEADER" directive and put a file named simply HEADER in the
directory to be indexed.  It will not be displayed.
>Fix:
Revert to the old way of handling HeaderName and ReadmeName, or at least
add an option to revert to the old method.
>Audit-Trail:
>Unformatted:
[In order for any reply to be added to the PR database, you need]
[to include <ap...@Apache.Org> in the Cc line and make sure the]
[subject line starts with the report component and number, with ]
[or without any 'Re:' prefixes (such as "general/1098:" or      ]
["Re: general/1098:").  If the subject doesn't match this       ]
[pattern, your message will be misfiled and ignored.  The       ]
["apbugs" address is not added to the Cc line of messages from  ]
[the database automatically because of the potential for mail   ]
[loops.  If you do not include this Cc, your reply may be ig-   ]
[nored unless you are responding to an explicit request from a  ]
[developer.  Reply only with text; DO NOT SEND ATTACHMENTS!     ]