Make sure that you allow override's for the directory you want to
protect with an .htaccess file.
If it is Allowoveride None, it will ignore the .htaccess file.
It is also possible to configure your access restrictions in the access.conf file
itself with an AllowOverride None. I forgot the exact syntax.
Hans
Igmar Palsenberg wrote:
>
> Hi,
>
> I have a problem with Apache:
>
> I used to have a password protected page. When I updated Apache to a new
> version, it overwrote my access.conf. Nog big deal, but the backup was
> accedently killed....
>
> To be short : It doesn't work anymore, and I don't have a clue.
>
> Here is my access.conf file :
>
> # access.conf: Global access configuration
> # Online docs at http://www.apache.org/
>
> # This file defines server settings which affect which types of services
> # are allowed, and in what circumstances.
>
> # Each directory to which Apache has access, can be configured with respect
> # to which services and features are allowed and/or disabled in that
> # directory (and its subdirectories).
>
> # Originally by Rob McCool
>
> # This should be changed to whatever you set DocumentRoot to.
>
> <Directory /home/httpd/html>
>
> # This may also be "None", "All", or any combination of "Indexes",
> # "Includes", "FollowSymLinks", "ExecCGI", or "MultiViews".
>
> # Note that "MultiViews" must be named *explicitly* --- "Options All"
> # doesn't give it to you (or at least, not yet).
>
> Options None
>
> # This controls which options the .htaccess files in directories can
> # override. Can also be "All", or any combination of "Options", "FileInfo",
> # "AuthConfig", and "Limit"
>
> AllowOverride None
>
> # Controls who can get stuff from this server.
>
> order allow,deny
> allow from all
>
> </Directory>
>
> # /usr/local/etc/httpd/cgi-bin should be changed to whatever your
> ScriptAliased
> # CGI directory exists, if you have that configured.
>
> <Directory /home/httpd/cgi-bin>
> AllowOverride None
> Options ExecCGI
> </Directory>
>
> # Allow server status reports, with the URL of
> http://servername/server-status
> # Change the ".your_domain.com" to match your domain to enable.
>
> <Location /server-status>
> SetHandler server-status
>
> order deny,allow
> deny from all
> allow from 192.168.1.100
> </Location>
>
> # Custom directory setup
> <Directory /home/httpd/html/lpg>
> AllowOverride None
> Options ExecCGI
> </Directory>
>
> <Directory /home/httpd/html/brumanual>
> AllowOverride None
> Options ExecCGI
> </Directory>
>
> # There have been reports of people trying to abuse an old bug from pre-1.1
> # days. This bug involved a CGI script distributed as a part of Apache.
> # By uncommenting these lines you can redirect these attacks to a logging
> # script on phf.apache.org. Or, you can record them yourself, using the
> script
> # support/phf_abuse_log.cgi.
>
> <Location /cgi-bin/phf*>
> deny from all
> ErrorDocument 403 http://phf.apache.org/phf_abuse_log.cgi
> </Location>
>
> # You may place any other directories or locations you wish to have
> # access information for after this one.
>
> This a a .htaccess file :
>
> AuthUserFile /password/brumanual/.htpasswd
> AuthName BRU Manual
> AuthType Basic
>
> <Limit GET>
> require user igmar
> </Limit>
>
> It doesn't work. Everyone has access..... It beats me !!!
>
> Anybody got a clue ??
>
> Igmar
>
> --
> PLEASE read the Red Hat FAQ, Tips, Errata and the MAILING LIST ARCHIVES!
> http://www.redhat.com/RedHat-FAQ /RedHat-Errata /RedHat-Tips /mailing-lists
> To unsubscribe: mail [EMAIL PROTECTED] with
> "unsubscribe" as the Subject.
--
PLEASE read the Red Hat FAQ, Tips, Errata and the MAILING LIST ARCHIVES!
http://www.redhat.com/RedHat-FAQ /RedHat-Errata /RedHat-Tips /mailing-lists
To unsubscribe: mail [EMAIL PROTECTED] with
"unsubscribe" as the Subject.
