I'm having problems with my Soap Server implemented on PHP on my production server (remote one).
I've implemented a simple Soap Server (native PHP class) with just on function on WSDL mode.
So my code looks like:
ini_set("soap.wsdl_cache_enabled", "0");
$server = new SoapServer("wsSeguimiento.wsdl");
$server->addFunction("ResultadoDetalleExtendido");
$server->handle();
Now, as you know, when you call the server via web-browser with the url like "http://localhost/soapserver/wsServer.php", you got a blank page - in my case - or whatever you've programmed there (server code).
But if you call the same URL with the "?wsdl" at the end "http://localhost/soapserver/wsServer.php?wsdl", then the server (handle function I guess) resolves the XML wsdl on the web browser, so you get a text/xml content type and you can see the XML definition itself.
Now, it works on my development environment. No problems. I've created a Soap client to test my own server, and to see if it return the expeted response, and everything works fine. But when I upload the code to the production server, it doesn't work.
Firefox shows on the url with "?wsdl" call, the typical error saying "XML malformed", but in this particular case it's from the beginning, like if there were no XML file at all. And if I use my client, I get the error:
SOAP-ERROR: Parsing WSDL: Couldn't load from 'http://.../SOAP_SERVER/seguimientoServer.php?wsdl' : Start tag expected, '<' not found
I've correctly changed namespaces and URLs in the WSDL XML file. So it have to work properly. But it doesn't.
I've found that there are existing bugs related with HTTP header itself, based on chunked data, content-length, X-powered-by, whatever...
But I don't see a solution.
I've done a little hack on my server based on this (after handle() call):
if( isset($_REQUEST['wsdl']) )
{
ob_clean();
echo file_get_contents( "wsSeguimiento.wsdl" );
}
And with this, it really works! But I'm sure that this doesn't have to be the way to solve it...
