|
|
php.net | support | documentation | report a bug | advanced search | search howto | statistics | random bug | login |
PatchesPull RequestsHistoryAllCommentsChangesGit/SVN commits
[2010-01-11 20:48 UTC] srinatar@php.net
[2010-01-13 13:34 UTC] srinatar@php.net
[2010-01-14 23:30 UTC] meatloafninja at gmail dot com
[2016-11-02 23:02 UTC] gcarrette at wayfair dot com
[2021-02-11 21:39 UTC] cmb@php.net
-Status: Open
+Status: Feedback
-Assigned To:
+Assigned To: cmb
[2021-02-11 21:39 UTC] cmb@php.net
[2021-02-21 04:22 UTC] php-bugs at lists dot php dot net
|
|||||||||||||||||||||||||||||||||||||
Copyright © 2001-2024 The PHP GroupAll rights reserved. |
Last updated: Thu Apr 18 18:01:28 2024 UTC |
Description: ------------ If you enable WSDL caching and set the cache type to 2 (memory) or 3 (both disk and memory), and create a SoapServer with a WSDL, and within the context of that SoapServer create multiple SoapClient connections to external web services with WSDLs (exceeding the soap.wsdl_cache_limit setting), the SoapServer's in-memory copy of its own WSDL will get removed / freed. This causes a segmentation fault of the web server child process or a corrupt / invalid XML response, as the SoapServer will be unable to access its own WSDL when the time comes to send its response to the original requesting client. The SoapServer WSDL should be protected from removal. Reproduce code: --------------- <?php ini_set('soap.wsdl_cache_enabled', 1); ini_set('soap.wsdl_cache', 3); function test($x) { $client1 = new SoapClient("http://some.other.host/client1.wsdl"); $client2 = new SoapClient("http://some.other.host/client2.wsdl"); $client3 = new SoapClient("http://some.other.host/client3.wsdl"); $client4 = new SoapClient("http://some.other.host/client4.wsdl"); $client5 = new SoapClient("http://some.other.host/client5.wsdl"); return $x; //web server segfaults or corrupt XML returned } $server = new SoapServer("server.wsdl"); $server->addFunction("test"); $server->handle(); ?> Expected result: ---------------- A valid XML response as defined by server.wsdl. Actual result: -------------- Either a segmentation fault on the web server and a "Could not fetch HTTP headers" error on the client, or a corrupted XML response.