Return-Path: Delivered-To: apmail-httpd-users-archive@www.apache.org Received: (qmail 94949 invoked from network); 6 Apr 2006 21:02:09 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 6 Apr 2006 21:02:09 -0000 Received: (qmail 37542 invoked by uid 500); 6 Apr 2006 21:02:02 -0000 Delivered-To: apmail-httpd-users-archive@httpd.apache.org Received: (qmail 37080 invoked by uid 500); 6 Apr 2006 21:02:00 -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: List-Id: Delivered-To: mailing list users@httpd.apache.org Received: (qmail 37069 invoked by uid 99); 6 Apr 2006 21:02:00 -0000 Received: from asf.osuosl.org (HELO asf.osuosl.org) (140.211.166.49) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 06 Apr 2006 14:02:00 -0700 X-ASF-Spam-Status: No, hits=1.3 required=10.0 tests=ML_MARKETING X-Spam-Check-By: apache.org Received-SPF: pass (asf.osuosl.org: local policy) Received: from [69.3.31.188] (HELO mail.loanprocessing.net) (69.3.31.188) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 06 Apr 2006 14:01:59 -0700 Received: from mojo (mojo.express.loanprocessing.net [192.168.1.108]) by mail.loanprocessing.net (8.13.6/8.13.4) with SMTP id k36L1Xp0012625 for ; Thu, 6 Apr 2006 14:01:34 -0700 Message-ID: <07af01c659bd$5b7b8330$6c01a8c0@mojo> From: "Mike McMullen" To: References: <07d701c658ee$ead8df20$6c01a8c0@mojo> Date: Thu, 6 Apr 2006 14:02:04 -0700 MIME-Version: 1.0 Content-Type: text/plain; format=flowed; charset="Windows-1252"; reply-type=response Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2900.2180 X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.2180 X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-2.0.2 (mail.loanprocessing.net [192.168.1.3]); Thu, 06 Apr 2006 14:01:34 -0700 (PDT) X-Baton-MailScanner-Information: Please contact support@loanprocessing.net for more information X-Baton-MailScanner: Found to be clean X-Baton-MailScanner-SpamCheck: not spam (whitelisted), SpamAssassin (score=-2.775, required 5, autolearn=not spam, ALL_TRUSTED -1.80, BAYES_00 -2.60, ML_MARKETING 1.62) X-Baton-MailScanner-From: mlm@loanprocessing.net X-Virus-Checked: Checked by ClamAV on apache.org Subject: Re: [users@httpd] Require differences between 2.0.53 and 2.2.0 X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N ----- Original Message ----- From: "Mike McMullen" To: Sent: Wednesday, April 05, 2006 1:24 PM Subject: [users@httpd] Require differences between 2.0.53 and 2.2.0 > > Hi All, > > I am putting in a new server to replace an old server we are using. > > The old server is running FC3 and Apache 2.0.53. > > The new server is running FC5 and Apache 2.2.0. > > We have a small user base and use .htaccess file to manage > access in people's public_html directories using "require user". > > We also have a small support staff that access user' public_html > directories with "require group". > > Under 2.0.53 in the .htaccess file we would have both the > "require group" and the "require user" lines. Both people > in the group and the named user could access the directory > just fine. > > Under 2.2.0 it appears that the last "require" line is the only > one that is allowed to access the folder. > Is there a setting or way to have both the "require group" and > the "require user" work? I want the access to be this user and > this group. > Some additional info, I have looked in the 2.2.0 server's ssl_error_log and I see the following error: access to /~someid failed, reason: user 'myid' does not meet 'require'ments for user/valid-user to be allowed access However, I have verified that 'myid' is in the staff group. The standard .htaccess file looks something like this: AuthName "Some User's Data" AuthType Basic AuthUserFile /Our/data/users AuthGroupFile /Our/data/groups require group staff require user someid If I remove the require user line I can access the folder by my id being in the groups file. Of course the user can't. Under 2.0.53 this works so that either the user or the people in the group can authenticate and access the data. What am I missing here? TIA Mike --------------------------------------------------------------------- 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