--- Begin Message ---
- To: Debian Bug Tracking System <submit@bugs.debian.org>
- Subject: apache2: lenny8 rev broke DirectoryIndex processing
- From: John Bazik <jsb@cs.brown.edu>
- Date: Wed, 30 Jun 2010 16:40:12 -0400
- Message-id: <20100630204012.24742.59745.reportbug@asdf.cs.brown.edu>
Package: apache2
Version: 2.2.9-10+lenny8
Severity: normal
With the update from lenny7 to lenny8 a few days ago, my apache server
began choosing the wrong DirectoryIndex files to serve. I have a
config snippet in /etc/apache2/conf.d/mod_dir that orders them like
this:
DirectoryIndex home.html home.htm home.shtml\
index.html index.htm index.shtml index.xml
Directories with only home.html files work fine, but index.html is now
preferred.
More weirdly, in debugging this, I removed the DirectoryIndex directive
from /etc/apache2/mods-available/dir.conf, and that fixed it. Since
that file is processed before my snippet, I would expect my snippet to
override it. Since home.html files *are* being processed, it seems like
the two directives are being combined instead.
I realize this makes no sense. I looked at the changelog. But I've
got two web servers with different but similar configs that are
both affected. And in both cases, the only thing that changed was the
new apache rev.
-- System Information:
Debian Release: 5.0.5
APT prefers stable
APT policy: (750, 'stable'), (70, 'oldstable')
Architecture: i386 (i686)
Kernel: Linux 2.6.26-2-686 (SMP w/4 CPU cores)
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)
Shell: /bin/sh linked to /bin/bash
Versions of packages apache2 depends on:
pn apache2-mpm-worker | apache2- <none> (no description available)
apache2 recommends no packages.
apache2 suggests no packages.
--- End Message ---
--- Begin Message ---
On Friday 02 July 2010, John Bazik wrote:
> On Fri, Jul 02, 2010 at 09:34:49PM +0200, Stefan Fritsch wrote:
> > If you have several DirectoryIndex statements in the same
> > section, they are merged. Only if you have DirectoryIndex
> > statements in different sections, the last section to be merged
> > wins. I strongly doubt that there was any behaviour change
> > caused by the update.
>
> Really? I wondered that, but couldn't find it documented anywhere.
I don't think it is explicitly documented. But the code is written
that way and there are a number of config directives which work in the
same way.
Closing the bug.
--- End Message ---