Re: mod_dir/9349: DirectoryIndex is broken in CGI directories

[wr...@apache.org]

[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!     ]


Synopsis: DirectoryIndex is broken in CGI directories

State-Changed-From-To: open-closed
State-Changed-By: wrowe
State-Changed-When: Mon Mar 25 23:16:01 PST 2002
State-Changed-Why:
Sounds like you simply forgot your AllowOverride directive.

Re: mod_dir/9349: DirectoryIndex is broken in CGI directories

[Andrew Wales <aw...@jasper.dryfish.org>]

On Tue, Mar 26, 2002 at 07:16:01AM -0000, wrowe@apache.org wrote:
> Synopsis: DirectoryIndex is broken in CGI directories
> 
> State-Changed-From-To: open-closed
> State-Changed-By: wrowe
> State-Changed-When: Mon Mar 25 23:16:01 PST 2002
> State-Changed-Why:
> Sounds like you simply forgot your AllowOverride directive.

Which AllowOverride directive would you recommend?  I already have

    AllowOverride FileInfo AuthConfig Limit Indexes Options

Surely Indexes should be enough?  And as I stated in the original
bug report, this setup worked fine in 1.3.12, and only broke when
I moved to 2.0.28.  Incidentally, I'm now on 2.0.32 and I'm still
seeing the same behaviour.

Thanks


Andrew

-- 
stan@meow.org.uk
http://www.meow.org.uk/stan/