Hmm... My thought would have been that Apache::AuthenCache would do the trick... What are the exact symptoms when you use AuthenCache? Are you still hitting the Domain controller for every request?
A long time ago I wrote this:
<snip> my problem:
I'm running a reverse proxy with apache 1.3.x and mod_proxy on debian. For the authentication libapache-authensmb is used, so there's a connection to the domain controller present and working. Everything is fine, but for each request sent by the browser, the module needs to authenticate on the nt-domain. As I was told, the domain controller can't handle all the requests, so it's compareble with an DOS-attack. Because of this, the browser opens multiple times the popup for filling in the authentication data (although it's not necessary). To prevent this, I tried the following ideas I have found in the web:
a) exclude images from being authenticated b) AuthenCache c) AuthzCache
Nothing helped... <snip>
Has this been fixed in the meanwhile?
Another option would be to use $r->is_initial_req like:
my $r = shift; return OK unless $r->is_initial_req;
What happens when you add this to the module? (I'm not sure that this would be appropriate in the main module on CPAN, but you could just add the line everytime you downloaded it... (What does everyone else think? Maybe set a PerlSetVar to turn this on and off?))
-- Shannon Eric Peevey => "speeves" Dyno-Mite! System Administrator => [EMAIL PROTECTED] Central Web Support => (940) 369-8876 University of North Texas => http://web2.unt.edu
-- Report problems: http://perl.apache.org/bugs/ Mail list info: http://perl.apache.org/maillist/modperl.html List etiquette: http://perl.apache.org/maillist/email-etiquette.html
