I've run into an interesting bug in mp1. If I have a PerlCleanupHandler
defined in a .htaccess file, then it won't run if there was a
PerlInitHandler defined in httpd.conf. It doesn't matter what the
PerlInitHandler does, as long as its there the cleanup fails. If I have
the init h
Trey Hyde wrote:
My PerlCleanupHandler seems to be firing before the content phase has
finished processing the page.
The handler pretty much looks like
sub handler {
my ($r) = @_;
undef $Foo::bar;
undef $Foo::baz;
return OK;
}
It's being invoked in a virtual host apache conf segment
My PerlCleanupHandler seems to be firing before the content phase has
finished processing the page.
The handler pretty much looks like
sub handler {
my ($r) = @_;
undef $Foo::bar;
undef $Foo::baz;
return OK;
}
It's being invoked in a virtual host apache conf segment with
PerlCleanupHa
Tom Murphy wrote:
I have written a Apache::DBILogger style log mechanism. It is enabled via
the perl.conf in the Server context as:
PerlCleanupHandler NC::LogHandler
It works correctly, except for the fact that request handle by the
default-handler do not call this handler. The mod_perl
I have written a Apache::DBILogger style log mechanism. It is enabled via
the perl.conf in the Server context as:
PerlCleanupHandler NC::LogHandler
It works correctly, except for the fact that request handle by the
default-handler do not call this handler. The mod_perl cookbook makes note
Jie Gao wrote:
Hi All,
On redhat 8 using mod_perl-1.99_05-3
I have the folloing in httpd.conf:
PerlCleanupHandler "sub { %ENV = () }"
in VirtualHost, and am getting:
Invalid command 'PerlCleanupHandler', perhaps mis-spelled or def
Hi All,
On redhat 8 using mod_perl-1.99_05-3
I have the folloing in httpd.conf:
PerlCleanupHandler "sub { %ENV = () }"
in VirtualHost, and am getting:
Invalid command 'PerlCleanupHandler', perhaps mis-spelled or defined by a module
Debian))
> id 181QC0-0001uo-00; Tue, 15 Oct 2002 04:48:56 -0700
> Date: Tue, 15 Oct 2002 04:48:56 -0700 (PDT)
> To: [EMAIL PROTECTED]
> Cc: [EMAIL PROTECTED], [EMAIL PROTECTED]
> Subject: Re: ap_rwrite()/ap_rvputs() called in PerlCleanupHandler
> X-URL: http://www.symonds
Thanks for reply ..
> Hello!
>
> internal_redirect()
> The required argument is an absolute URI path on the current server.
> The server will process the URI as if it were a whole new request,
> running the URI translation, MIME type checking, and other phases
> before invoking the appropria
Hello again.
May be it helps to solve your problem.
is_initial_req()
There are several instances in which an incoming URI request can
trigger one or more secondary internal requests. An internal request
is triggered when internal_redirect() is called explicitly, and it
also happens behind the sce
Hello!
internal_redirect()
The required argument is an absolute URI path on the current server.
The server will process the URI as if it were a whole new request,
running the URI translation, MIME type checking, and other phases
before invoking the appropriate content handler for the new URI.
Hello,
I have a mod_perl application which does a internal_redirect() and registers a
cleanup handler before returning. I am noticing that the cleanup handler
executes and i see the following in my log ..
[Tue Oct 15 03:27:32 2002] [info] [client XYZ ] (9)Bad file number: client
stopped conn
On Fri, 11 Aug 2000, Tim Sweetman wrote:
> I've seen something similar - when the client browser times out,
> execution seems to stop mid-Print statement, and mod_Perl gets ready for
> the next request, without cleaning up objects present (or, at least,
> without calling ->DESTROY).
this should
On Wed, 9 Aug 2000, Michael Peppler wrote:
> Hi,
>
> We're seeing a number of requests where the write from apache to the
> client browser times out and the SIGALRM signal fires. Our
> Apache::Registry scripts in that case don't clean up correctly,
> leaving session lock files around, which of c
Subject: push_handlers (was: PerlCleanupHandler vs register_cleanup)
>
>
> While we're on the subject of handlers, if
> I have
> PerlLogHandlers moda modb modc
> in my conf file
> and I do
> $r->push_handlers('PerlLogHandler', \&d);
>
that the stacked log handlers run?
-P
> -Original Message-
> From: Stas Bekman [mailto:[EMAIL PROTECTED]]
> Sent: Thursday, August 24, 2000 12:47 PM
> To: Paul G. Weiss
> Cc: modperl
> Subject: Re: PerlCleanupHandler vs register_cleanup
>
>
> On Thu, 24 Au
On Thu, 24 Aug 2000, Paul G. Weiss wrote:
> What is the difference between doing
> $r->push_handlers('PerlCleanupHandler', \&function);
> and
> $r->register_cleanup(\&function);
The same:
http://www.modperl.com/book/chapters/ch9.html#Server_Core_Func
What is the difference between doing
$r->push_handlers('PerlCleanupHandler', \&function);
and
$r->register_cleanup(\&function);
Hi,
Michael Peppler wrote:
> We're seeing a number of requests where the write from apache to the
> client browser times out and the SIGALRM signal fires. Our
> Apache::Registry scripts in that case don't clean up correctly,
> leaving session lock files around, which of course causes that
> parti
Hi,
We're seeing a number of requests where the write from apache to the
client browser times out and the SIGALRM signal fires. Our
Apache::Registry scripts in that case don't clean up correctly,
leaving session lock files around, which of course causes that
particular session to be screwed up fo
20 matches
Mail list logo
