<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
<META NAME="Generator" CONTENT="MS Exchange Server version 6.5.7650.28">
<TITLE>RE: [Melbourne-pm] mod_perl and apache authentication</TITLE>
</HEAD>
<BODY>
<!-- Converted from text/plain format -->
<P><FONT SIZE=2>Thanks Dave<BR>
<BR>
Does order of installation refer to order it is declared in the httpd.conf (or .htaccess) file, or is it based on the directory that the rule applies to (i.e. according to specificity). I'm guessing the former, but I've gotten access to change my httpd.conf, and putting the LDAP stuff first (i.e. earlier installation?) in the conf file does not help.<BR>
<BR>
Everything works beautifully when that LDAP auth stuff is not there. If all else fails, I'm thinking of altering the LDAP auth to apply only to a subdirectory (not overlapping with the one I am working on setting up auth for), because strictly speaking, that is probably all that it is really required for.<BR>
<BR>
Thanks<BR>
<BR>
--<BR>
Gary<BR>
<BR>
-----Original Message-----<BR>
Okay, it's been a long time since i've done any apache module<BR>
programming, but my copy of the Eagle book says that when you have<BR>
stacked handlers for the same phase (in this case the authentication<BR>
phase, the first handler to respond with OK or AUTH_REQUIRED causes all<BR>
the other handlers to be skipped, otherwise, the handler can return<BR>
DECLINED to allow the next handler to check the request. However, the<BR>
server will call the handlers in reverse order of installation. <BR>
Hopefully this helps.<BR>
<BR>
Best of luck<BR>
-Dave<BR>
<BR>
_______________________________________________<BR>
Melbourne-pm mailing list<BR>
Melbourne-pm@pm.org<BR>
<A HREF="http://mail.pm.org/mailman/listinfo/melbourne-pm">http://mail.pm.org/mailman/listinfo/melbourne-pm</A><BR>
<BR>
<BR>
</FONT>
</P>
</BODY>
</HTML>