Received: (qmail 5910 invoked by uid 2012); 9 Sep 1999 17:09:52 -0000 Message-Id: <19990909170952.5908.qmail@hyperreal.org> Date: 9 Sep 1999 17:09:52 -0000 From: Thijs Kinkhorst Reply-To: thijs@kinkhorst.com To: apbugs@hyperreal.org Subject: HEADER and README files not used when generating directory listings X-Send-Pr-Version: 3.2 >Number: 4988 >Category: mod_autoindex >Synopsis: HEADER and README files not used when generating directory listings >Confidential: no >Severity: non-critical >Priority: medium >Responsible: apache >State: closed >Quarter: >Keywords: >Date-Required: >Class: sw-bug >Submitter-Id: apache >Arrival-Date: Thu Sep 9 10:10:00 PDT 1999 >Closed-Date: Fri Jan 14 12:06:34 PST 2000 >Last-Modified: Fri Jan 14 12:06:34 PST 2000 >Originator: thijs@kinkhorst.com >Release: 1.3.9 >Organization: >Environment: Linux 2.2.12 i386 >Description: The contents of the files named HEADER and README used to be pre/appended to the dirlistings generated by mod_autoindex. In evrsion 1.3.9, this suddenly stopped working. I've seen this bug reported twice in the database but it was to my perception misinterpreted by the handling "official". >How-To-Repeat: http://beta.jaze.net/bug-demo/ http://beta.jaze.net/bug-demo/HEADER http://beta.jaze.net/bug-demo/README The contents of the HEADER and README files should display in the dirlisting of the first url, but they don't. >Fix: Negative. >Release-Note: >Audit-Trail: State-Changed-From-To: open-closed State-Changed-By: coar State-Changed-When: Fri Jan 14 12:06:34 PST 2000 State-Changed-Why: This issue is being tracked in report #4991. >Unformatted: [In order for any reply to be added to the PR database, you need] [to include 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! ]