Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:26092
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: error (pb1.pair.com: domain rooftopsolutions.nl from 66.207.192.7 cause and error)
Message-ID: <4537C21F.9070900@rooftopsolutions.nl>
Date: Thu, 19 Oct 2006 14:21:19 -0400
Reply-To: evert@rooftopsolutions.nl
User-Agent: Thunderbird 1.5.0.7 (Macintosh/20060909)
MIME-Version: 1.0
To: internals@lists.php.net
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Subject: Feature request: ini setting for http 500 on fatal errors
From: evert@rooftopsolutions.nl (Evert | Rooftop)

Excuse me if this has been discussed before, but I would like to know 
the stance on this issue, it's hard to search the buglist or mailing 
archives on stuff like http, 500 and fatal.

Would it be hard to implement an ini setting for throwing a http 500 
error on a fatal error? It's hard to make certain applications and have 
proper error handling if there is no way to do anything on a fatal error..

It would be even grander if php could try to run a fall-back script when 
something really bad happens, but just having that 500 on fatal errors 
would be awesome ..

If this is not going to happen anytime soon, would you accept a patch?

Evert