Description:
------------
We have a wide-spread problem with errors causing the script to just fail and Apache returning http 200. Trouble is that 200 means certain things for some of the bindings.

Many of us run with display_errors off in php.ini and therefore
when a php error occurs we just get nothing in return and a 200.
All sorts of things can cause this - a missing include, a syntax
error, etc.

I run with display_errors on, so I get back text that is intended
for the browser: <b>Fatal Error</b> and so on.

This at least tells me something is up, but in fact the code
usually just tries to chew on the text and treat it as an atom
response, xmlrpc response, jsonrpc response etc. This is not
usually much better.

The problem is widespread and in the json and xmlrpc code.