Edit report at https://bugs.php.net/bug.php?id=64704&edit=1
ID: 64704 Comment by: welfordmartin at gmail dot com Reported by: welfordmartin at gmail dot com Summary: Problem with ASP.NET Soap Servers Status: Open Type: Bug Package: SOAP related Operating System: All PHP Version: 5.3.24 Block user comment: N Private report: N New Comment: Recommended Fix: It would be nice if there was an option in setting up the SoapClient that tells it to use inline xmlns instead of in Envelope namespacing Previous Comments: ------------------------------------------------------------------------ [2013-04-24 16:07:57] welfordmartin at gmail dot com Description: ------------ This might want changing to a Feature Request instead of bug but I'm not sure. There is a problem in ASP.NET SOAP Server that for some reason does not support using the Envelope xmlns:ns stuff inside the soap:header this is how php SoapClient works <soap:Envelope ... xmlns:ns1="" xmlns:ns2=""> ASP.NET uses <soap:header> <Method xmlns=""> </Method> </soap:header> Please look at "The Test Scripts" for the problem that occures these are not the php code but the payload generated by SoapClient and the manual modifications i had to to to get the code to work on my REST Testing client. Test script: --------------- Working: http://pb.mgawow.co.uk/yvxCQe2S Not Working PHP SoapClient Generated: http://pb.mgawow.co.uk/r9xjaEW4 Expected result: ---------------- Working API Call Actual result: -------------- Fails causes a 500 error on remote server called ------------------------------------------------------------------------ -- Edit this bug report at https://bugs.php.net/bug.php?id=64704&edit=1
