Edit report at https://bugs.php.net/bug.php?id=69293&edit=1
ID: 69293
Comment by: ks dot sundarajan at capgemini dot com
Reported by: andre at tomt dot net
Summary: NEW segfault when using SoapClient::__setSoapHeader
(bisected, regression)
Status: Closed
Type: Bug
Package: SOAP related
Operating System: Linux Ubuntu 14.04 x86_64
PHP Version: 5.5Git-2015-03-24 (Git)
Assigned To: laruence
Block user comment: N
Private report: N
New Comment:
Hello,
Can you please tell us in version of php is this fix available? Is this fix released?
Thanks,
Sundar
Previous Comments:
------------------------------------------------------------------------
[2015-04-06 00:38:01] stas@php.net
Automatic comment on behalf of dmitry@zend.com
Revision: http://git.php.net/?p=php-src.git;a=commit;h=75f40ae1f3a7ca837d230f099627d121f9b3a32f
Log: Fixed bug #69293
------------------------------------------------------------------------
[2015-03-31 16:43:26] cmb@php.net
Related To: Bug #69341
------------------------------------------------------------------------
[2015-03-27 15:43:31] dmitry@php.net
Automatic comment on behalf of dmitry@zend.com
Revision: http://git.php.net/?p=php-src.git;a=commit;h=75f40ae1f3a7ca837d230f099627d121f9b3a32f
Log: Fixed bug #69293
------------------------------------------------------------------------
[2015-03-27 13:35:36] karl at debisschop dot net
requinix - it seems the problem is that a security fix has broken the SOAP module because the
applied patch had a flaw. It's not about making changes to 5.4 -- it's about making
changes to the flaws in the security patch. Is there no room to fix the patch or are we to make the
SOAP system potentially unusable because policy prohibits us from applying a corrected patch?
------------------------------------------------------------------------
[2015-03-27 10:21:12] requinix@php.net
As of a few months ago, 5.4 is only intended to get security fixes.
http://php.net/supported-versions.php
------------------------------------------------------------------------
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=69293
--
Edit this bug report at https://bugs.php.net/bug.php?id=69293&edit=1