You are viewing a plain text version of this content. The canonical link for it is here.
Posted to modperl@perl.apache.org by Hadmut Danisch <ha...@danisch.de> on 2007/02/22 20:49:50 UTC

PerlAuthenHandler called twice?

Hi,

just a minor question:


I am currently porting an older authentication module written some years ago
for Apache1.3 and perlmod to Apache2.2 and perlmod2. 


For some reason the module is called twice for every request. 



The old version checked $r->is_initial_req and $r->is_main to detect
subrequests.


Now I do check $r->is_initial_req() to be true and $r->main() to return
undefined/false values, but still get every request twice. 


As far as I understood the docs, the PerlAuthenHandler is not called in the
response phase. But what's the reason for being called twice?

regards
Hadmut

 

Re: PerlAuthenHandler called twice?

Posted by Sumit Shah <ss...@gce2000.com>.
I am getting a similar problem. Its invoking my handler twice for the 
same request. I am using PerlAccessHandler.

Thanks
Sumit

Robert Landrum wrote:
> Hadmut Danisch wrote:
>> For some reason the module is called twice for every request.
>
> Is this a HEAD/GET problem?  Maybe you're seeing the browser doing a 
> HEAD request, then a full GET request?
>
> Rob


Re: PerlAuthenHandler called twice?

Posted by Hadmut Danisch <ha...@danisch.de>.
On Thu, Feb 22, 2007 at 04:18:35PM -0500, Robert Landrum wrote:
> Hadmut Danisch wrote:
> >For some reason the module is called twice for every request. 
> >
> 
> Is this a HEAD/GET problem?  Maybe you're seeing the browser doing a 
> HEAD request, then a full GET request?


No, I have checked this. Only one get (also with wget), only one entry in the 
access.log. 


Actually I am not sure whether the procedure is really called twice. It is just that output from log_error appears twice. Maybe it doubles all log entries?

regards
Hadmut

Re: PerlAuthenHandler called twice?

Posted by Robert Landrum <rl...@aol.net>.
Hadmut Danisch wrote:
> For some reason the module is called twice for every request. 
> 

Is this a HEAD/GET problem?  Maybe you're seeing the browser doing a 
HEAD request, then a full GET request?

Rob