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
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
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
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
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
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
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
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) --
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
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/redirects anywhere in my
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 an
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 an
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
13 matches
Mail list logo
