httpd-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Rob Hartill <hart...@hyperreal.com>
Subject Apache 0.8.6 (fwd)
Date Tue, 08 Aug 1995 01:21:10 GMT

I'm answering all the "easy" questions. I'll keep bouncing anything
for which I haven't a clue to the list...

btw, don't tell me the answers, tell the users.

-=-=-=-=

Forwarded message:

> From archie@tribe.com  Mon Aug  7 17:01:44 1995
> From: Archie Cobbs <archie@tribe.com>
> Message-Id: <199508080000.RAA11254@bubba.tribe.com>
> Subject: Apache 0.8.6
> To: apache-bugs@mail.apache.org
> Date: Mon, 7 Aug 1995 17:00:50 -0700 (PDT)
> X-Mailer: ELM [version 2.4 PL24]
> Content-Type: text
> Content-Length: 2429      
> 
> 
> Thanks for a great program, it's a lot of fun to play with.
> 
> I'm using version 0.8.6 and am getting a reference to
> a NULL pointer on line 185 of "mod_auth_dbm.c". I tried to
> figure some stuff out using gdb and the -X option.
> 
> I'm not sure if what I'm trying to do is supposed to be
> possible or not, so I'm not sure if this is really a bug.
> 
> Here the relevant snippet of code from "mod_auth_dbm.c":
> 
>     int dbm_check_auth(request_rec *r) {
>         dbm_auth_config_rec *sec =
>           (dbm_auth_config_rec *)get_module_config (r->per_dir_config,
>                             &dbm_auth_module);
>         char *user = r->connection->user;
>         int m = r->method_number;
>         char errstr[MAX_STRING_LEN];
>         
>         array_header *reqs_arr = requires (r);
> 185>>>  require_line *reqs = (require_line *)reqs_arr->elts;
> 
> What's happening is that requires(r) returns NULL, so line 185 bombs.
> The URL requested in this case is just "/" and access.conf contains
> the following verse for DocumentRoot, which is "/home/www/htdocs":
> 
>     <Directory /home/www/htdocs>
> 
>         Options         Indexes FollowSymLinks Includes ExecCGI
>         AllowOverride   None
> 
>         AuthName        mail
>         AuthType        Basic
>         AuthUserFile    /home/www/htpasswd
>         AuthGroupFile   /dev/null
> 
>         <Limit GET>
>             order deny,allow
>             deny from all
>             allow from .tribe.com
>         </Limit>
> 
>     </Directory>
> 
> Notice, no "require" line.  The reason I have this is because there
> are subdirectories for which I'd like to restrict access to individual
> users by having, for example,
> 
>     ###
>     ### User archie's subdirectory
>     ###
> 
>     <Directory /home/www/htdocs/archie>
>         Options ExecCGI
>         AllowOverride None
>         <Limit GET>
>             require user archie
>         </Limit>
>     </Directory>
> 
> But there would only be a single password file, authetication
> type, etc. I realize a workaround is to put the Auth* lines in
> each individual user's <Directory> verse.
> 
> Is this supposed to work? My understanding of <Directory> that it
> works for all subdirectories, except where superceded by a more
> "precise" <Directory> verse (containing more path elements).
> So the AuthName, AuthType, etc. above would be inherited by all the
> subdirectories.
> 
> Is this the proper way to think of <Directory> ? Maybe I made that
> leap without proper justification.
> 
> Thanks for any clarification.
> 
> -Archie
 

Mime
View raw message