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

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

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 handlers

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. So

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 403

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

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 = shift; my

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 whatever) --

teste

2003-03-14 Thread Rangel, Luciano
teste

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 will return an

[Http-webtest-general] [ANNOUNCE] HTTP-WebTest-Plugin-TagAttTest-1.00

2003-03-14 Thread Ed Fancher
The uploaded file HTTP-WebTest-Plugin-TagAttTest-1.00.tar.gzhas entered CPAN as file: $CPAN/authors/id/E/EF/EFANCHE/HTTP-WebTest-Plugin-TagAttTest-1.00.tar.gz size: 5312 bytes md5: 940013aada679fdc09757f119d70686e NAME HTTP::WebTest ::Plugin::TagAttTest - WebTest plugin providing a