Thanks, Justin. That was the problem! I added '?wsdl' and the SOAP errors
are gone.
David Roth
On Tue, Jun 11, 2013 at 1:12 PM, Justin Dearing wrote:
> That is a non-WCF ASP.NET service. It should be foo.asmx?wsdl for the
> wsdl. you can use fiddler or Charles to inspect the SOAP packets if you
That is a non-WCF ASP.NET service. It should be foo.asmx?wsdl for the wsdl.
you can use fiddler or Charles to inspect the SOAP packets if you continue
to have troubles
On Jun 11, 2013 12:49 PM, "Donald Organ" wrote:
> Thats probably becaus ethats not the URL to the WSDL, can you go to that
> url
Thats probably becaus ethats not the URL to the WSDL, can you go to that
url in a browser, generally you can and then there is a link that will
bring you to the WSDL.
On Tue, Jun 11, 2013 at 12:02 PM, David Roth wrote:
> There is a server which supports SOAP, that ends in .asmx such as
> http://
There is a server which supports SOAP, that ends in .asmx such as
http://example.com/foo.asmx. I'm getting these kind of PHP error messages:
PHP Fatal error: SOAP-ERROR: Parsing WSDL: Couldn't load from '
http://example.com:8090/foo.asmx' : Premature end of data in tag html line 3
in /home/www/h
