Thanks for the reply. Yeah, this is what I'm worried about, that I'm missing something really simple.
I think I'm basically doing what you suggest; the request passes through my perl code that performs the authorization checks, and if they are satisfied, my code then calls mod_status via the (awkward) subrequest I described. I did this because I don't understand how to use server configuration directives to get the request to pass first through my perl code for auth*tion, then have the response generated by mod_status. Unless... I have just been assuming that one can't use Perl*Handler directives unless using "SetHandler perl-script". Can I still set a PerlAuth*Handler in a <Location> if I have "SetHandler server-status" there? Hmm... Charlie On Tuesday 22 August 2006 3:44 pm, you wrote: > Charlie Katz wrote: > > On Tuesday 22 August 2006 3:37 pm, Charlie Katz wrote: > >> <Location /server-status> > >> SetHandler server-status > >> ... > >> Allow from ... > >> </Location> > >> > >> doesn't work for me because I don't want to control access based on URI, > >> but rather the custom authorization level my site assigns when a user > >> logs in. > > > > Oops, I meant to say "... because I don't want to control access based on > > IP address, but rather ..." > > I'm confused as to yhy can't you just the custom auth you already have? > Just use PerlAuth*Handler directives. -- Charlie Katz Harvard-Smithsonian Center for Astrophysics [EMAIL PROTECTED]
