Re: Tracing double accesshandler invocation

2003-03-14 Thread Nick Tonkin
On Fri, 14 Mar 2003, Richard Clarke wrote: > > > sub handler { > > > my $r = shift; > > > my $uri = $r->the_request; > > > return OK unless $r->is_initial_req; # stops dbl execution > > > > "Stops dbl execution" _after_ this point, of course. If you request a > > directory, the server

Re: Tracing double accesshandler invocation

2003-03-14 Thread Richard Clarke
> > sub handler { > > my $r = shift; > > my $uri = $r->the_request; > > return OK unless $r->is_initial_req; # stops dbl execution > > "Stops dbl execution" _after_ this point, of course. If you request a > directory, the server will return an internal redirect to $dir/index.html > (or

Re: Tracing double accesshandler invocation

2003-03-14 Thread Geoffrey Young
Also, I think it's better to return DECLINED from your Access handler if you're not returning FORBIDDEN, rather than OK, since there may be other handlers that need to work on the request. And if not now, maybe in the future. all access handlers run so long as everyone returns an Apache success co

Re: Tracing double accesshandler invocation

2003-03-14 Thread Nick Tonkin
On Fri, 14 Mar 2003, Richard Clarke wrote: > package AC::Centry::Access; > $AC::Centry::Access::VERSION = qw$Revision: 1.2 $[1]; > > use strict; > use Apache::Constants qw(:common); > use AC::Centry::Tool(); > > # handler() > # Process requests to protected URI's > sub handler { > my $r = shif

Re: Tracing double accesshandler invocation

2003-03-14 Thread Richard Clarke
package AC::Centry::Access; $AC::Centry::Access::VERSION = qw$Revision: 1.2 $[1]; use strict; use Apache::Constants qw(:common); use AC::Centry::Tool(); # handler() # Process requests to protected URI's sub handler { my $r = shift; my $uri = $r->the_request; return OK unless $r->is_in

Re: Tracing double accesshandler invocation

2003-03-14 Thread Nick Tonkin
On Fri, 14 Mar 2003, Richard Clarke wrote: > > The only thing which it does which is affected by anything outside of its > > immediate environment is call, $r->prev. This shouldn't call the > > accesshandler though... should it? > > > > Erm, doh, not sure why I said this. This only happens when a

Re: Tracing double accesshandler invocation

2003-03-14 Thread Richard Clarke
> The only thing which it does which is affected by anything outside of its > immediate environment is call, $r->prev. This shouldn't call the > accesshandler though... should it? > Erm, doh, not sure why I said this. This only happens when a 403 happens and the user is sent to the /login location

Re: Tracing double accesshandler invocation

2003-03-14 Thread Richard Clarke
Nick, > if ($r->lookup_uri($r->uri)->content_type =~ /image/) { > return Apache::DECLINED; > } > > > Do you have this, or something similar, in your code? I greped my entire directory tree for any of the subrequest mechanisms and the only place I am using them are in some hand

Re: Tracing double accesshandler invocation

2003-03-14 Thread Geoffrey Young
Nick Tonkin wrote: Hi Ric, This has been a nightmare trying to debug, but I think I've found where the cause is in my module. In my Access handler I have some code designed to skip Access handling for images (let the html pages take care of that). The code calls $r->lookup_uri to check on the co

RE: Tracing double accesshandler invocation

2003-03-14 Thread Nick Tonkin
Hi Ric, This has been a nightmare trying to debug, but I think I've found where the cause is in my module. In my Access handler I have some code designed to skip Access handling for images (let the html pages take care of that). The code calls $r->lookup_uri to check on the content type of the f

Re: Tracing double accesshandler invocation

2003-03-06 Thread Nick Tonkin
On Thu, 6 Mar 2003, Stas Bekman wrote: > Nick Tonkin wrote: > > On Wed, 5 Mar 2003, Richard Clarke wrote: > > > > > >>Hi, > >>I'm trying to figure out why my accesshandler is getting triggered twice > >>for each request that I make. I'm 100% sure that I'm doing no explicit > >>lookups/redirect

Re: Tracing double accesshandler invocation

2003-03-05 Thread Stas Bekman
Nick Tonkin wrote: On Wed, 5 Mar 2003, Richard Clarke wrote: Hi, I'm trying to figure out why my accesshandler is getting triggered twice for each request that I make. I'm 100% sure that I'm doing no explicit lookups/redirects anywhere in my code. The particular uri I am fetching should only i

Re: Tracing double accesshandler invocation

2003-03-05 Thread Nick Tonkin
On Wed, 5 Mar 2003, Richard Clarke wrote: > Hi, > I'm trying to figure out why my accesshandler is getting triggered twice > for each request that I make. I'm 100% sure that I'm doing no explicit > lookups/redirects anywhere in my code. The particular uri I am fetching > should only invocate a

Re: Tracing double accesshandler invocation

2003-03-05 Thread Nick Tonkin
On Wed, 5 Mar 2003, Richard Clarke wrote: > Hi, > I'm trying to figure out why my accesshandler is getting triggered twice > for each request that I make. I'm 100% sure that I'm doing no explicit > lookups/redirects anywhere in my code. The particular uri I am fetching > should only invocate a

Tracing double accesshandler invocation

2003-03-05 Thread Richard Clarke
Hi, I'm trying to figure out why my accesshandler is getting triggered twice for each request that I make. I'm 100% sure that I'm doing no explicit lookups/redirects anywhere in my code. The particular uri I am fetching should only invocate an accesshandler followed by a contenthandler. After w