He he : ) I think this discussion is being miscommunicated (if that is a relevant word). I do not want authorization to be performed in the typical manner. Perhaps I want the information from a form submit or a cookie. I understand how the Apache authentication configuration works but I want to strictly use mod_perl to modify the authentication mechanisms without the standard Apache intervention.
> You mean you want to do authorization in a FixupHandler?? No, this is what I currently have to do to avoid Apache from sending the 'auth request' headers to the browser and still perform custom authentication via a form submit, cookie, etc. Thanks, > > : ) No problem, I guess I am unsure if this is the proper way > to setup an > > Access, Authen, Authz handler. When I use this configuration > my 'handler()' > > method does not get called and I get an error in the logs: > > [Mon Dec 10 13:13:03 2001] [crit] [client 192.168.0.1] > configuration error: > > couldn't check user. No user file?: /index.html > > I think Apache is looking for the wrong file. Check the config > for AuthUserFile. > Did you use htpasswd to create it? > > > I tried moving it down to be an Authz handler but the same error occurs. > > However, if I push this package as a FixupHandler it works fine and the > > 'handler()' method gets called. > > You mean you want to do authorization in a FixupHandler?? > > If you like I can let you have some scripts which will show you one way of > checking for authorization without a second request for a > username/password, > assuming that at some stage in the browser session one was > already supplied. > Is that what you meant? > > 73, > Ged. > >
