Return-Path: Delivered-To: apmail-httpd-users-archive@www.apache.org Received: (qmail 1861 invoked from network); 18 Feb 2005 07:22:02 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur-2.apache.org with SMTP; 18 Feb 2005 07:22:02 -0000 Received: (qmail 7053 invoked by uid 500); 18 Feb 2005 07:21:52 -0000 Delivered-To: apmail-httpd-users-archive@httpd.apache.org Received: (qmail 6755 invoked by uid 500); 18 Feb 2005 07:21:50 -0000 Mailing-List: contact users-help@httpd.apache.org; run by ezmlm Precedence: bulk Reply-To: users@httpd.apache.org list-help: list-unsubscribe: list-post: Delivered-To: mailing list users@httpd.apache.org Received: (qmail 6739 invoked by uid 99); 18 Feb 2005 07:21:50 -0000 X-ASF-Spam-Status: No, hits=0.2 required=10.0 tests=NO_REAL_NAME X-Spam-Check-By: apache.org Received-SPF: pass (hermes.apache.org: local policy) Received: from email.itcilo.org (HELO email.itcilo.org) (195.47.232.25) by apache.org (qpsmtpd/0.28) with ESMTP; Thu, 17 Feb 2005 23:21:49 -0800 In-Reply-To: <42151CDB.10208@hostinthebox.net> To: users@httpd.apache.org MIME-Version: 1.0 X-Mailer: Lotus Notes Release 6.5.1 January 21, 2004 Message-ID: From: g.lams@itcilo.org Date: Fri, 18 Feb 2005 08:21:59 +0100 X-MIMETrack: Serialize by Router on ITC-DOMINO/ITCILO/IT(Release 6.5.1|January 21, 2004) at 18/02/2005 08.22.04, Serialize complete at 18/02/2005 08.22.04 Content-Type: text/plain; charset="ISO-8859-1" Content-Transfer-Encoding: quoted-printable X-Virus-Checked: Checked Subject: Re: [users@httpd] .htaccess, AllowOverride X-Spam-Rating: minotaur-2.apache.org 1.6.2 0/1000/N Strange, it should work. Did you try to put inside a directory directive=20 what you have inside you htaccess file? Something like this: # Directives to password protect the AWStats reports AuthType Basic AuthName Gurn AuthUserFile /srv/www/htpasswd-gurn Require valid-user Does it work? Ga=EBl dan wrote on 17/02/2005 23.38.19: > Hello, all - >=20 > I'm a bit rusty on .htaccess, and I am not able to find this answer=20 > anywhere. >=20 > By default, "AllowOverride" is set to "None" for inside=20 > httpd.conf, we all know this. When modifying AllowOverride on a=20 > per-directory basis inside a VirtualHost container, shouldn't those=20 > paramaters set forth inside the VirtualHost container override the=20 > defaults? I've found this not to be true, unfortunately, and wondering=20 > what the rule is - which specification takes precidence? Is this by=20 > design, or am I doing something wrong with trying to set "AllowOverride=20 > (insert option here)" options? >=20 > I know this is kindof a dumb question, and I believe I knew the answer=20 > once upon a time. The reason why I'm asking is that I do not want to=20 > set "AllowOverride (insert option here)" as the default, which is what I = > have done a couple times in the past to satisfy this occourance. >=20 > Thanks for the time > -dant >=20 > --------------------------------------------------------------------- > The official User-To-User support forum of the Apache HTTP Server=20 Project. > See for more info. > To unsubscribe, e-mail: users-unsubscribe@httpd.apache.org > " from the digest: users-digest-unsubscribe@httpd.apache.org > For additional commands, e-mail: users-help@httpd.apache.org >=20 --------------------------------------------------------------------- The official User-To-User support forum of the Apache HTTP Server Project. See for more info. To unsubscribe, e-mail: users-unsubscribe@httpd.apache.org " from the digest: users-digest-unsubscribe@httpd.apache.org For additional commands, e-mail: users-help@httpd.apache.org