From nobody@hyperreal.com Sun Apr 20 12:51:47 1997 Received: (from nobody@localhost) by hyperreal.com (8.8.4/8.8.4) id MAA11709; Sun, 20 Apr 1997 12:51:47 -0700 (PDT) Message-Id: <199704201951.MAA11709@hyperreal.com> Date: Sun, 20 Apr 1997 12:51:47 -0700 (PDT) From: Lars Eilebrecht Reply-To: sfx@unix-ag.org To: apbugs@hyperreal.com Subject: Strange behaviour of IndexOptions X-Send-Pr-Version: 3.2 >Number: 430 >Category: config >Synopsis: Strange behaviour of IndexOptions >Confidential: no >Severity: non-critical >Priority: medium >Responsible: apache >State: closed >Class: doc-bug >Submitter-Id: apache >Arrival-Date: Sun Apr 20 13:00:01 1997 >Last-Modified: Sun Jun 29 18:22:08 PDT 1997 >Originator: sfx@unix-ag.org >Organization: >Release: 1.2b8 >Environment: Linux/i586 2.0.29 >Description: srm.conf-dist contains the entry IndexIgnore */.??* *~ *# */HEADER* */README* */RCS But what's the reason for the "*/" syntax, eg. "*/README" instead of just "README"? At least for me the following entry produces the same result like the entry from srm.conf-dist: IndexIgnore .??* *~ *# HEADER* README* RCS Maybe this is a bug, because the documentation of IndexIgnore talks about 'partial filenames' and 'file extensions' which seems not to work, eg. ".txt" does not hide "foobar.txt", but only ".txt". P.S.: IMHO "core" should always be hidden. Maybe it's a good idea to add this to the IndexIgnore entry in your srm.conf-dist file. >How-To-Repeat: >Fix: If it's a bug - fix the bug... if not - fix the documentation. ;-%2 >Audit-Trail: From: Dean Gaudet To: Lars Eilebrecht Subject: Re: config/430: Strange behaviour of IndexOptions Date: Sun, 20 Apr 1997 15:40:25 -0700 (PDT) Starting with 1.2b9 the following protects cores better than using IndexIgnore: order deny,allow deny from all (Although that specific case might work in b8, but a bug fix went in for it in b9.) I'll let someone else deal with the doc issue. Dean Class-Changed-From-To: mistaken-doc-bug Class-Changed-By: coar@decus.org Class-Changed-When: Fri Apr 25 02:56:17 PDT 1997 State-Changed-From-To: open-analyzed State-Changed-By: coar State-Changed-When: Sat Apr 26 16:25:28 PDT 1997 State-Changed-Why: A brief examination of the code does seem to indicate that the leading "*/" may be superfluous. The .conf-dist and/or documentation may not be corrected until a release after 1.2, but this will definitely be looked at more closely. State-Changed-From-To: analyzed-closed State-Changed-By: dgaudet State-Changed-When: Sun Jun 29 18:22:08 PDT 1997 State-Changed-Why: srm.conf-dist in 1.3 won't contain the paths. Even though it's silly for mod_dir to accept them, it just ignores the path if present. But that's just one more notch on the "mod_dir silliness list". Dean >Unformatted: