Date:  Sun, 06 Jan 2008 17:39:52 -0600
From:  Brent Epp <brent (at mark) pdcweb.net>
Subject:  [coba-e:11669] Re: Can't access web root as default index  (apache directory  listing)
To:  coba-e (at mark) bluequartz.org
Message-Id:  <634ejo$25hj45 (at mark) wnpgmb01-c600f.mts.net>
In-Reply-To:  <478005E1.1040706 (at mark) dogsbody.org>
References:  <634ejo$25eb14 (at mark) wnpgmb01-c600f.mts.net> <478005E1.1040706 (at mark) dogsbody.org>
X-Mail-Count: 11669

Thanks, that did it!

Having this change on updates is not a big deal for me, since I'm 
just using this on a personal dev server.

Thanks
  - Brent

At 2008-01-05 16:34, Dogsbody wrote:

>>I get this error message when I attempt to access an empty web root 
>>directory (eg.: /home/sites/www.example.com/web/) when it does not 
>>contain a default index file like index.html, index.php, etc.
>>"You don't have permission to access / on this server."
>>I know this never used to happen until recently.  Was there an 
>>update that changed this?  How can I change it back so that I can 
>>view the apache directory listing?
>
>This took me ages to work out what was happening, simple fix....
>
>mv /etc/httpd/conf.d/manual.conf /etc/httpd/conf.d/manual.conf.off
>mv /etc/httpd/conf.d/welcome.conf /etc/httpd/conf.d/welcome.conf.off
>/etc/rc.d/init.d/httpd reload
>
>The trouble is that these files will come back each time httpd is 
>updated via yum.  Instead of moving manual.conf you can also do a 
>`yum remove httpd-manual` which will permanently remove it but I 
>don't know how to permanently remove welcome.conf.  Anyone else know?
>
>The silly thing is that due to the way BlueQuartz is set up neither 
>of these configs actually work anyway.
>
>Just for clarity, this only affects indexes for the root directory of a site!
>
>Dan
>
>


Brent Epp
mailto:brent (at mark) pdcweb.net