Bug #75586 [NoF->Csd]: WSDL parsing issue throws a fatal error instead of a SOAPFault exception

Edit report at https://bugs.php.net/bug.php?id=75586&edit=1 ID: 75586 User updated by: ryan dot jentzsch at gmail dot com Reported by: ryan dot jentzsch at gmail dot com Summary: WSDL parsing issue throws a fatal error instead of a SOAPFault exception -Status: No Feedback +Status: Closed Type: Bug Package: SOAP related Operating System: Linux Mint 18.3 -PHP Version: 7.1.12 +PHP Version: 7.1.18 Block user comment: N Private report: N New Comment: running php -n is not useful since PHP will not compile dying on Line 2: Fatal error: Class 'SoapClient' not found in /home/ryan/wsdl.php on line 2 Now without the -n switch PHP emits a warning, and then PHP commits suicide: ``` PHP Warning: SoapClient::SoapClient(): I/O warning : failed to load external entity "bogus" in /home/ryan/wsdl.php on line 7 PHP Stack trace: PHP 1. {main}() /home/ryan/wsdl.php:0 PHP 2. SoapAgent->__construct() /home/ryan/wsdl.php:15 PHP 3. SoapAgent->SoapClient() /home/ryan/wsdl.php:7 PHP Fatal error: SOAP-ERROR: Parsing WSDL: Couldn't load from 'bogus' : failed to load external entity "bogus" in /home/ryan/wsdl.php on line 7 PHP Stack trace: PHP 1. {main}() /home/ryan/wsdl.php:0 PHP 2. SoapAgent->__construct() /home/ryan/wsdl.php:15 PHP 3. SoapAgent->SoapClient() /home/ryan/wsdl.php:7 ``` Previous Comments: ------------------------------------------------------------------------ [2018-06-24 04:25:38] php-bugs at lists dot php dot net No feedback was provided. The bug is being suspended because we assume that you are no longer experiencing the problem. If this is not the case and you are able to provide the information that was requested earlier, please do so and change the status of the bug back to "Re-Opened". Thank you. ------------------------------------------------------------------------ [2017-11-28 21:41:42] nikic@php.net I can't reproduce this issue: The exception object is successfully dumped. Please check whether your code works under php -n, and if it does, try to identify which extension is responsible for the behavior. My guess would be that the xdebug error handler interferes here. ------------------------------------------------------------------------ [2017-11-28 21:33:04] ryan dot jentzsch at gmail dot com Description: ------------ Subclassing the SoapClient class and wrapping the call to the parent constructor will throw a fatal error even when wrapped in a try...catch(\Throwable $t). With PHP 7 try...catch(\Throwable $t) being a convenient method of adding fault tolerance and graceful degradation -- it is therefore very frustrating when a WSDL PARSE issue is encountered that an UNCATCHABLE script exiting fatal error is issued. Related: 60780, 45093, (XDEBUG specific: 34657, 49587) SO "work-around": https://stackoverflow.com/questions/6952814/php-soap-error-catching Test script: --------------- <?php class SoapAgent extends \SoapClient { public function __construct(string $wsdl) { try { parent::__construct($wsdl); echo 'Success!' . PHP_EOL; } catch (\Throwable $t) { var_dump($t); } } } $client = new SoapAgent('bogus'); Expected result: ---------------- var_dump() of the Throwable object. Actual result: -------------- Fatal error: SOAP-ERROR: Parsing WSDL: Couldn't load from 'bogus' : failed to load external entity "bogus" Process finished with exit code 255 ------------------------------------------------------------------------ -- Edit this bug report at https://bugs.php.net/bug.php?id=75586&edit=1