Re: custom_response/segfaults

[Doug MacEachern]

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)

custom_response/segfaults

[Paul]

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/