----- Original Message -----
From: Bolt Thrower <[EMAIL PROTECTED]>
> <Location />
> AuthType Apache::AuthTicket
> AuthName HomeIntranet
> PerlAuthenHandler Intranet::CheckSiteAuthen
> #PerlAuthenHandler Apache::AuthTicket->authenticate
> PerlAuthzHandler Apache::AuthTicket->authorize
> require valid-user
> </Location>
> But when I try to access a location under that configuration,
> I see in my error log:
> [Mon Jun 25 18:33:55 2001] [crit] [client 192.168.10.15] configuration
> error: couldn't
> check user. No user file?: /u/IntranetLoginForm
mod_auth supplies the "Auth*" dirrectives. Since he sees 'require
valid-user', he's looking for the rest of the Auth* directives.
Specifically, "AuthUserFile".
I have a handler doing just what you are describing, and have the same
problem. My solution was to mandate that my mudule was the only thing
allowed to use Auth* configureation in the server config file and that
everybody else had to use .htaccess. But I still see that message
occasionally. My suggestion: if it work, then ignore the error message. :-)
> Of course, everything works with the configuration
> <Location />
> AuthType Apache::AuthTicket
> ...
> </Location>
> Any suggestions for me?
Yep, Auth* happens at the Directory level. From the docs:
AuthUserFile
Context: directory, .htaccess
So, if you have an other set of Auth* directives in the same scope, then
that can cause conflicts
---
Rodney Broom
Programmer: Desert.Net
