Reply. I put print statements in the mod_auth_digest file to see values. I didn't see subsequent call, but I forgot to check the timestamps.
I'll look again. Thanks. Margaret Michele Waldman Sovereign Sites L.L.C. Website Development 646-861-3375 Rule your domain ... -----Original Message----- From: Ray Morris [mailto:supp...@bettercgi.com] Sent: Friday, April 10, 2009 7:06 PM To: modules-dev@httpd.apache.org Subject: Re: mod_auth_digest You won't see anything special on the Apache side, I don't think. I believe the only difference between the first authentication and subsequent requests is that the browser (hopefully) sends the user/pass with each request, so there is no need for Apache to return a 401, causing the clinet to pop up the authentication dialog and re-request the page with the authentication info the secodn time around. -- Ray B. Morris supp...@bettercgi.com Strongbox - The next generation in site security: http://www.bettercgi.com/strongbox/ Throttlebox - Intelligent Bandwidth Control http://www.bettercgi.com/throttlebox/ Strongbox / Throttlebox affiliate program: http://www.bettercgi.com/affiliates/user/register.php On 04/10/2009 04:33:23 PM, Michele Waldman wrote: > Does anyone know? > > After a browser calls a page authenticated with mod_auth_digest, what > function or hook is called the next time the page is accessed. > > I figure it has to authenticate each time, but it's probably using a > short > cut to reauthenticate. I want to intervene but I'm not sure what's > getting > called on subsequent page accesses. > > Thanks, > > Michele > >
