On 8/16/05, Tim Traver <tt-list@xxxxxxxxxxxxx> wrote: > Hi all, > > ok, quick question. I want to make some configuration changes so that > the whole directory path is not walked to look for .htaccess files to > improve performance. > > I currently have a custom module that I have made that sets the Document > root based on host names, and it is a relatively long path. > > The path usually looks something like this : > > /shared/accounts/d/o/m/a/domain.com/site/htdocs > > Now, I know that there won't be the need for any .htaccess files for > anywhere above the "site" directory, but I want users to be able to use > them in the "site" and "htdocs" directory. > > Is there a way to tell apache to allow this in these couple of > directories without specifically naming these full directories ? Since > the Document root paths are set in my apache module, I can't put a > <Directory> tag for each directory. > > Would <DirectoryMatch> do it ??? would that prevent apache from looking for No, in fact AllowOverride is a special case directive that works only in ordinary <Directory> sections. See: http://httpd.apache.org/docs/2.0/sections.html#whatwhere But, assuming your structure uses the same number of levels for all sites, you can use a wildcard (not a regex) which is allowed in <Directory> sections. For example: <Directory /> AllowOverride None </Directory> <Directory /shared/accounts/*/*/*/*/*/site/> AllowOverride All </Directory> Joshua. --------------------------------------------------------------------- The official User-To-User support forum of the Apache HTTP Server Project. See <URL:http://httpd.apache.org/userslist.html> for more info. To unsubscribe, e-mail: users-unsubscribe@xxxxxxxxxxxxxxxx " from the digest: users-digest-unsubscribe@xxxxxxxxxxxxxxxx For additional commands, e-mail: users-help@xxxxxxxxxxxxxxxx
|