Hi all, It doesn't much matter whether you're using stacked handlers or not, or pushing vs. replacing, because the $r->child_terminate method seems to simply call the C exit(0) function under certain conditions (Win32, old version of apache, anything else?). Not much chance of any further action if that's happening.
Under "normal" conditions child_terminate() is just supposed to set: requests_this_child = ap_max_requests_per_child = 1; which shouldn't be a problem. Geoffrey Young <[EMAIL PROTECTED]> wrote: > > >> -----Original Message----- >> From: Perrin Harkins >> To: Alex Harper >> Cc: Daniel; [EMAIL PROTECTED] >> Sent: 10/1/01 11:35 PM >> Subject: Re: CGI.pm params not being cleared? >> >> Alex Harper wrote: >>> >>> Aha! That's where the problem lies. I had recently added: >>> PerlCleanupHandler +Apache::Sizelimit >>> >>> to my httpd.conf. I placed it there so the sizelimit would be enforced >>> post-request. Removing the line fixed my problem. >> >> Whoa! This could be bad. Apache::SizeLimit calls >> $r->post_connection(). Is that replacing existing cleanup handlers? I >> thought post_connection()/register_cleanup() pushed handlers on the >> stack rather than replacing them. > > you know, I just tested this this afternoon - register_cleanup does push > handlers onto the stack. however, I have read a few bug reports in the > archives that mention bugs along these lines - that sometimes the cleanup > phase seems to allow only one handler. I know Randal mentioned it once, > but IIRC it was 2+ years ago... > > FWIW > > --Geoff