www-mirrors mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Obantec Support" <supp...@obantec.net>
Subject Re: Mirror changes killed my mirror
Date Fri, 24 May 2002 14:36:01 GMT

with just "AllowOverride FileInfo Indexes" i get 403 forbidden on /dist/

adding "Options Indexes" fixes this.
this is how http://apache.obantec.com is currently running.

<Directory /home/domain/domain7/web/>
  IndexOptions FancyIndexing NameWidth=* FoldersFirst ScanHTMLTitles
  HeaderName HEADER.html
  ReadmeName README.html
AllowOverride FileInfo Indexes
Options Indexes

just a though but are we fighting .htaccess here? i.e. if mirror has older
code and we make changes to apache and don't update until next cron update?

----- Original Message -----
From: "Joshua Slive" <joshua@slive.ca>
To: <mirrors@apache.org>
Sent: Friday, May 24, 2002 3:16 PM
Subject: Re: Mirror changes killed my mirror

> On Fri, 24 May 2002, Henk P. Penning wrote:
> >   -- I think requiring 'AllowOverride all' is wrong,
> >      because of the security implications.
> >      It shouldn't even be considered.
> >      If the requirement stays, many mirrors will give up.
> >
> >   -- The current settings place some limits on the
> >      de developpers (httpd, xml, etc) but they are
> >      not unreasonable.
> Ok.  I went back to AllowOverride FileInfo Indexes.  In reality, the
> AllowOverride directive is not really flexible enough.  By removing
> "Options", I'm preventing CGI scripts and SSI pages, but we can still
> access filters and handlers through FileInfo.  Ah well.
> Joshua.

View raw message