> ... exccept taht will give you the authenticated user name, as in, the name
> entered at the Authentication phase.
When I said: $r->connection->user($user), I meant you can use this to _set_
the user, regardless of whether you used an auth handler or not.
Sorry for being unclear.
$r->connection->user('CHOLET');
> When Nicholas says the authentication
> is handled at the "script level", I assume that he means that it is handled
> during the content generation phase. I would write a separate module or
> registry script and put that in place as a PerlAuthenHandler. All it has to
> do is return AUTH_REQUIRED to deny access, OK to allow access, based on
> whatever means you are using (cookies are available at this point, you just
> can't send HTML to the browser), or DECLINED to let Apache or another custom
> module handle it.
>
> After this point, yes, $r->connection->user will give you the username that
> was entered, and ($r->get_basic_auth_pw)[1] will return the password that
> was entered.
>
> darren
>
> Eric ([EMAIL PROTECTED]) wrote:
> > On Fri, Jan 07, 2000 at 10:59:10AM +0100, Nicolas MONNET wrote:
> > >
> > > I am using a cookie based authentification mechanism, the authentification
> > > is handled at the script (Apache::Registry) level. Is there a way to pass
> > > the info to logging mechanism so that I can have my "user" value passed as
> > > if it was transmitted to Apache as an HTTP authentification?
> >
> > Yes: $r->connection->user($user);
> >
> > >
> > > --
> > > Nicolas MONNET, Technical Director, IT-Xchange
> >
> > --
> > Eric Cholet
>
> --
> If all the world is a stage, where is the audience sitting?
--
Eric CHOLET
