perl-modperl mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From kropotkin <enquir...@mms-oxford.com>
Subject Re: die problem in mod_perl
Date Fri, 12 Sep 2008 22:38:44 GMT

Hi Perrin

Thanks again. This is most helpful.

I've now wrapped the top level call in an eval block and that works fine.
Just one problem though - print STDERR is printing the message to the main
server error log not the virtual host error log. die printed it to the
virtual host error log. It doesn't really matter as only I not clients will
be looking at the log but it is a frustration.


regards

Kropotkin







Perrin Harkins wrote:
> 
> On Fri, Sep 12, 2008 at 5:14 PM, kropotkin <enquiries@mms-oxford.com>
> wrote:
>> True; I could pass return values
>> back up the chain and at the top-level if there was a problem do return
>> "OK"
>> there to cancel execution without generating a 500 error but this would
>> be a
>> pain to manage.
> 
> Then catch the die in an eval at a level where you can return OK to
> apache.
> 
>> I found an easier solution - which may of course not be the 'best' one: I
>> still call die in my custom error handling routine which generates a 500
>> error. But I've used the Apache ErrorDocument directive to kill of the
>> default error message and replace it with my own (I found out it takes
>> text
>> as well as a file).  I just pass it a period, and that's it.
> 
> That's not a good solution.  What if there was an unexpected error in
> some other code?  You would never know.
> 
> - Perrin
> 
> 

-- 
View this message in context: http://www.nabble.com/die-problem-in-mod_perl-tp19462854p19465331.html
Sent from the mod_perl - General mailing list archive at Nabble.com.


Mime
View raw message