ID: 42773
User updated by: tjerk dot meesters at muvee dot com
Reported By: tjerk dot meesters at muvee dot com
Status: Assigned
Bug Type: SOAP related
Operating System: Linux 2.6
PHP Version: 5.2.4
Assigned To: dmitry
New Comment:
The proposed solution in bug #42722 to make the status 500 depend on
whether display errors is enabled doesn't help my problem.
In my case, no errors should be displayed at all because this would
interfere with the otherwise clean output of json_encode().
Previous Comments:
------------------------------------------------------------------------
[2007-09-27 09:48:02] [EMAIL PROTECTED]
See also bug #42722
------------------------------------------------------------------------
[2007-09-27 09:47:16] [EMAIL PROTECTED]
Dmitry, this is propably related to the change with errors causing 500
error change you did.
------------------------------------------------------------------------
[2007-09-27 03:40:42] tjerk dot meesters at muvee dot com
Description:
------------
Failure to load a WSDL file using the SoapClient class causes more than
just an exception. The error is also caught by the error handler and a
500 status code is sent back.
This error is classified as a PHP Fatal error and can't be caught by
any custom error handlers.
This error shouldn't be triggered at all, that's what we have
exceptions for ;-)
Reproduce code:
---------------
<?php
try {
$s = new SoapClient('http://localhost/invalid_wsdl');
} catch (Exception $e) {
echo $e->getMessage();
}
?>
Expected result:
----------------
SOAP-ERROR: Parsing WSDL: Couldn't load from
'http://localhost/invalid_wsdl'
Actual result:
--------------
[HTTP/1.x 500 Internal Server Error]
PHP Fatal error: SOAP-ERROR: Parsing WSDL: Couldn't load from
'http://localhost/invalid_wsdl' in /var/www/html/test.php on line 4
SOAP-ERROR: Parsing WSDL: Couldn't load from
'http://localhost/invalid_wsdl'
------------------------------------------------------------------------
--
Edit this bug report at http://bugs.php.net/?id=42773&edit=1
