Return-Path: owner-new-httpd Received: by taz.hyperreal.com (8.6.10/8.6.5) id BAA07668; Tue, 4 Apr 1995 01:02:44 -0700 Received: from chalmers.se by taz.hyperreal.com (8.6.10/8.6.5) with SMTP id BAA07597; Tue, 4 Apr 1995 01:01:26 -0700 Received: from fyserv1.fy.chalmers.se by chalmers.se (5.60+IDA/3.14+gl) id AA16796; Tue, 4 Apr 95 10:01:13 +0200 Date: Tue, 4 Apr 1995 10:01:15 +0200 From: Andy Polyakov Message-Id: <9504040801.AA17134@fyserv1.fy.chalmers.se> Received: by fyserv1.fy.chalmers.se (5.0/3.14+gl) id AA17134; Tue, 4 Apr 1995 10:01:15 +0200 To: new-httpd@hyperreal.com Subject: Re: httpd patches X-Sun-Charset: US-ASCII Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Content-Length: 1134 Sender: owner-new-httpd@hyperreal.com Precedence: bulk Reply-To: new-httpd@hyperreal.com > > NO, IT WON'T! At least not with NCSA 1.3: for cycle takes care of that. > > Hmmm... as I read the code, it will start checking for .htaccess files > in *subdirectories* of the directory named by the longest initial > substring which matches some directive in access.conf (or > DocumentRoot --- but that may be redundant). (Whew!) ??? NCSA httpd 1.3 always(!) starts searching .htaccesses from /. At least with default access.conf... So as apache_0.4, just checked. What have you got in access.conf? > > So, if every user home directory is a subdirectory of some other > directory named in access.conf, then httpd won't waste time walking > from root to those home directories. However, if some users have home > directories elsewhere (and at my site, they do), it will go straight > down the root, hitting the automounter paths (among others). Fortunately each ~user reference leaves corresponding alias in 'a' array in http_alias.c and that's what I use to localize .htaccess search to users' subtrees: for cycle in tackle_on_docroot goes through aliases and locates corresponding real path. Andy.