Bug #70469 [Opn->Csd]: SoapClient generates E_ERROR even if exceptions=1 is used

Edit report at https://bugs.php.net/bug.php?id=70469&edit=1 ID: 70469 Updated by: nikic@php.net Reported by: Steve at bedezign dot com Summary: SoapClient generates E_ERROR even if exceptions=1 is used -Status: Open +Status: Closed Type: Bug Package: SOAP related Operating System: Centos PHP Version: 5.6.13 Block user comment: N Private report: N New Comment: Automatic comment on behalf of a.artmnv@gmail.com Revision: http://git.php.net/?p=php-src.git;a=commit;h=1dfcd1af9aab9b760d971ceeac18e9e83c85f80f Log: Fixed bug #70469 Previous Comments: ------------------------------------------------------------------------ [2017-11-04 14:28:58] ant dot artamonov at gmail dot com Solved in PR: https://github.com/php/php-src/pull/2899 ------------------------------------------------------------------------ [2016-06-20 10:02:56] mail at cebe dot cc An example script to reproduce the issue can be found here: https://github.com/yiisoft/yii2/issues/11772#issuecomment-226991044 ------------------------------------------------------------------------ [2015-09-10 13:50:23] Steve at bedezign dot com Description: ------------ On an input request error, the SoapClient calls trigger_error with an error level of E_ERROR (which is deemed fatal according to https://secure.php.net/manual/en/errorfunc.constants.php). This also occurs with 'exceptions' enabled (so it does both trigger_error() and throws an exception. Since specifying faulty input for a soap call is definitely not a fatal error I think this is a bug. It causes weird behavior in Yii2 for example (see issue here: https://github.com/yiisoft/yii2/issues/9650 Test script: --------------- Hard to do since we are talking about internal soap services here. I've added a screenshot of the issue here: https://cloud.githubusercontent.com/assets/231572/9788585/2c23c0f4-57cb-11e5-9624-b54e9a48dc4b.png Expected result: ---------------- When "exception" == 1 I except trigger_error not to be called at all, and definitely not as a fatal error. Actual result: -------------- A call to trigger_error, causing issues in the fatal error handler of some libraries ------------------------------------------------------------------------ -- Edit this bug report at https://bugs.php.net/bug.php?id=70469&edit=1