On Thu, 28 Sep 2000, Bill Moseley wrote:
Nope. I just downloaded a fresh 1.24, and 1.3.12 and built with
ah, it happens for non-Registry handlers. patch below fixes. you can
also change your handler to:
sub handler {
my $r = shift;
$r-exit(HTTP_NOT_MODIFIED);
}
BTW
At 01:25 PM 04/20/00 -0700, Doug MacEachern wrote:
On Wed, 12 Apr 2000 [EMAIL PROTECTED] wrote:
Hi All,
...
[Mon Apr 10 22:27:01 2000] [error] at
/usr/lib/perl5/site_perl/5.005/i386-linux/Apache/SIG.pm line 31.
Line 31 is Apache::exit($s);
Apache::exit() calls die() underneath to halt
On Thu, 28 Sep 2000, Bill Moseley wrote:
Is there a way to make that message go away?
maybe if you can give me a small example that reproduces the message. it
works fine for me:
shift-send_http_header;
print "hi\n";
exit;
print "bye\n";
nothing in the error_log.
actually, the patch
At 01:43 PM 09/28/00 -0700, Doug MacEachern wrote:
On Thu, 28 Sep 2000, Bill Moseley wrote:
Is there a way to make that message go away?
maybe if you can give me a small example that reproduces the message. it
works fine for me:
package My::Hello;
use strict;
use Apache::Constants
On Wed, 12 Apr 2000 [EMAIL PROTECTED] wrote:
Hi All,
Recently I installed Apache-1.3.12 with mod_perl-1.22. Standard
installation. Everything seemed to work great.
I'm using the directive
PerlFixupHandler Apache::SIG
because you have some 'alive' scripts that need to be killed if
On Wed, 12 Apr 2000 [EMAIL PROTECTED] wrote:
Hi All,
Recently I installed Apache-1.3.12 with mod_perl-1.22. Standard
installation. Everything seemed to work great.
I'm using the directive
PerlFixupHandler Apache::SIG
because you have some 'alive' scripts that need to be killed if
on 4/12/00 6:08 PM, [EMAIL PROTECTED] at
[EMAIL PROTECTED] wrote:
Why is my address in there
See -
[EMAIL PROTECTED]
- FCCJ * 501 W State St * Jacksonville, Fl 32202 * 904/632-3089 -
Hi All,
Recently I installed Apache-1.3.12 with mod_perl-1.22. Standard
installation. Everything seemed to work great.
I'm using the directive
PerlFixupHandler Apache::SIG
because you have some 'alive' scripts that need to be killed if
the user closes his browser.
Well, everything seems to
