manual.conf does not interferer with index listing for me. (I can go to
http://sitename/welcome/ and get an apache manual).
welcome.conf on the other hand will never be compatible with directory
indexing since it has "Options -Indexes" in it.
My workaround was to comment that line out, and hope that new
over-writes will instead be handled by the "rpmnew" mechanism inside RPM
Regards,
Greg.
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
>
>
>