Return-Path: Delivered-To: apache-bugdb-archive@hyperreal.org Received: (qmail 15994 invoked by uid 6000); 17 Sep 1998 23:20:03 -0000 Received: (qmail 15810 invoked by uid 2001); 17 Sep 1998 23:20:01 -0000 Received: (qmail 15558 invoked by uid 2012); 17 Sep 1998 23:18:37 -0000 Message-Id: <19980917231837.15557.qmail@hyperreal.org> Date: 17 Sep 1998 23:18:37 -0000 From: Bill Houle Reply-To: bhoule@sandiegoca.ncr.com To: apbugs@hyperreal.org X-Send-Pr-Version: 3.2 Subject: mod_autoindex/3026: No way to change ReadmeName/HeaderName suffixes. Sender: apache-bugdb-owner@apache.org Precedence: bulk >Number: 3026 >Category: mod_autoindex >Synopsis: No way to change ReadmeName/HeaderName suffixes. >Confidential: no >Severity: non-critical >Priority: medium >Responsible: apache >State: open >Class: change-request >Submitter-Id: apache >Arrival-Date: Thu Sep 17 16:20:00 PDT 1998 >Last-Modified: >Originator: bhoule@sandiegoca.ncr.com >Organization: apache >Release: 1.3.1 >Environment: UNIX assumed. Specifics irrelevant. >Description: ReadmeName/HeaderName assume .html suffix, which causes problems in DOS 8.3 environments which have standardized on .htm as the text/html suffix. The feature is not accessible in this limited world. (This is semi-serious to those of us supporting DOS clients, but in the grand scheme of things, I guess its non-critical. :) >How-To-Repeat: >Fix: Either add ReadmeNameSuffix/HeaderNameSuffix directives (or similar) so one can specify an explicit suffix, of change the ReadmeName/HeaderName directory processing to iterate through all valid text/html suffixes configured for that server. The former might be semi-easy but require config file changes everywhere. The latter would be totally cool, but probably more difficult to implement. >Audit-Trail: >Unformatted: [In order for any reply to be added to the PR database, ] [you need to include in the Cc line ] [and leave the subject line UNCHANGED. This is not done] [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! ]