You are viewing a plain text version of this content. The canonical link for it is here.

Posted to modperl@perl.apache.org by Paul <yd...@yahoo.com> on 2000/06/01 18:00:24 UTC

custom_response/segfaults

After code verifying that the user hasn't already
been registered/approved, I changed the code below
==============================================
if ($url !~ /NewReg[.]cgi$/o) {
   $r->custom_response(FORBIDDEN,
       "/public/NewReg.cgi");
   return FORBIDDEN; # trigger custom_response
}
==============================================
to 
==============================================
return OK 
   if $url =~ m{  # (I removed a few patterns here)
                .*NewReg.cgi 
               }ixo;
   $r->headers_out->add('Location' =>
       "$serverpath/NewReg.cgi");
   return MOVED;
==============================================
and my segfaults seem to have stopped killing my
server child provcesses.
Did I use custom_response incorrectly?

__________________________________________________
Do You Yahoo!?
Send instant messages & get email alerts with Yahoo! Messenger.
http://im.yahoo.com/

Re: custom_response/segfaults

Posted by Doug MacEachern <do...@covalent.net>.

On Thu, 1 Jun 2000, Paul wrote:

> After code verifying that the user hasn't already
> been registered/approved, I changed the code below
> ==============================================
> if ($url !~ /NewReg[.]cgi$/o) {
>    $r->custom_response(FORBIDDEN,
>        "/public/NewReg.cgi");
>    return FORBIDDEN; # trigger custom_response
> }
> ==============================================
> to 
> ==============================================
> return OK 
>    if $url =~ m{  # (I removed a few patterns here)
>                 .*NewReg.cgi 
>                }ixo;
>    $r->headers_out->add('Location' =>
>        "$serverpath/NewReg.cgi");
>    return MOVED;
> ==============================================
> and my segfaults seem to have stopped killing my
> server child provcesses.
> Did I use custom_response incorrectly?

you're using it the right way.  which Perl*Handler are you calling it
from?  can you get a stacktrace?  (see SUPPORT doc)