Bug #42214 [Com]: SoapServer sends clients internal PHP errors
| From: | driezasson at me dot com | Date: | Fri, 03 Jul 2015 12:35:42 +0000 |
| Subject: | Bug #42214 [Com]: SoapServer sends clients internal PHP errors | ||
| References: | 1 | Groups: | php.bugs |
| Request: | Send a blank email to php-bugs+get-194100@lists.php.net to get a copy of this message | ||
Edit report at https://bugs.php.net/bug.php?id=42214&edit=1
ID: 42214
Comment by: driezasson at me dot com
Reported by: stuart dot caie at gmail dot com
Summary: SoapServer sends clients internal PHP errors
Status: Closed
Type: Bug
Package: SOAP related
Operating System: Ubuntu
PHP Version: 5.2.4RC1
Assigned To: dmitry
Block user comment: N
Private report: N
New Comment:
The 'send_errors' option is not mentioned in the manual page:
http://php.net/manual/en/class.soapserver.php
Hopefully, I at least found this bug report and realized, that this option really works. Would it be
possible, please, to add a mention of this undocumented feature to the documentation? I believe it
would help other desperate developers too.
Previous Comments:
------------------------------------------------------------------------
[2010-07-11 23:55:41] webmaster at guestwho dot com
Is it at least possible to add filename and error number to error messages ? I often run into
"call to member function on non-object" and I have a dozen possible classes that this
could occur in. The soapfaul generated by PHP doesn't contain filename nor line number, so
I'm flying blind (no way to debug php fatal errors that happen during a SOAP call).
------------------------------------------------------------------------
[2007-09-05 11:23:29] dmitry@php.net
Fixed in CVS HEAD and PHP_5_2.
Now you can disable to send errors back to client.
$server = new SoapServer(NULL,
array('uri' => 'http://localhost/server.php',
'send_errors' => false));
------------------------------------------------------------------------
[2007-09-03 10:56:21] jani@php.net
Usually when PHP hits a fatal error (that means _FATAL_ :) it's in such state that continuing
script run would be causing e.g. crash or the engine is about to blow up in some other way.
Don't bother submitting bug report about that, it will not change. (I think there's
already one about it too..)
Assigned back to Dmitry.
------------------------------------------------------------------------
[2007-08-31 15:11:38] stuart dot caie at gmail dot com
Yes, I would like the soap extension to let me hide fatal error messages. Please add that option,
either in code or in the php.ini
I still think PHP itself needs to be fixed so it can continue running user code after a fatal error.
However, that is a bigger change and less likely to be done. I'll look to see if such a bug is
already raised, otherwise I'll raise that as another bug.
Thanks
Stuart
------------------------------------------------------------------------
[2007-08-31 12:44:10] dmitry@php.net
PHP is not able to execute user-code after a fatal error.
The only thing I can do with this - provide a special SoapServer option to hide error messages. In
this case it always will send "[SOAP-ENV:Server] Internal error".
Do you like such solution?
------------------------------------------------------------------------
The remainder of the comments for this report are too long. To view
the rest of the comments, please view the bug report online at
https://bugs.php.net/bug.php?id=42214
--
Edit this bug report at https://bugs.php.net/bug.php?id=42214&edit=1