Cannot parse WSDL from Add web service description screen [#2418623]

Hi everyone,

I'm running DKAN on Ubuntu which runs on Drupal 7.34. I have downloaded the wsclient and http_client module on my desktop, transferred them to the DRUPAL_BASE/sites/all/modules, and then enabled the modules from Drupal's UI. When I tried to follow the example from I get the following error (attached screenshot):

Error parsing the WSDL file: SOAP-ERROR: Parsing WSDL: Couldn't load from 'http://www.w3schools.com/webservices/tempconvert.asmx?WSDL' : Premature end of data in tag html line 1

I also tried using the dev version of wsclient but had the same issue. Can anybody direct me to what I should be looking at?

Thanks

Comment	File	Size	Author
	wsclient error.png	25.98 KB	noelcusc

Support from Acquia helps fund testing for Drupal Acquia logo

Comments

Comment #1

LeoVe CreditAttribution: LeoVe commented 2 February 2015 at 16:57

I don't know if it helps, but I just installed the module also and used the url, it works fine with me.
Also using Drupal 7.34.

Comment #2

dman CreditAttribution: dman commented 2 February 2015 at 20:33

How is your firewall?
That's the sort of message I see when running a site in a 'safe' environment that can't get out.
Either because your host is locked up nice and tight, or because it needs a proxy to get to the outside world.

From the machine you are trying to run this from, can you wget that URL directly? Can you successfully run Drupals module update check?

Comment #3

noelcusc CreditAttribution: noelcusc commented 3 February 2015 at 10:34

Yes I am behind a firewall, and actually I do have trouble with the Update module. As you suggested, I tried to retrieve the W3schools WSDL using wget from the server and in fact I got a response from our authentication server. So for some reason apt-get can get through but other traffic is being blocked.

Then I tried using the URL of a WSDL within our network and it worked. So probably it is an issue with our security settings. I'll check it out with our engineers and let you know if I fixed it. Thanks a lot.

Comment #4

dman CreditAttribution: dman commented 3 February 2015 at 10:39

Apt-get targets can be whitelisted, or configured to use other protocols like FTP.
It's common enough for enterprise-size webservers to be "secure by default" until exceptions are identified.
Yes, in the first instance check with your network team so you know what you are working with. That's the necessary step.

We *try* to respect and support the proxy settings that Drupal core supports (read your settings.php for the configs "External access proxy settings" and adjust them until at least Drupal update works.) but as those cases are pretty edge and custom and pretty hard to set up to reliably test for, it's possible that support for unexpected scenarios (eg authentication needed through a proxy when we are hand-rolling a cURL request) may not be all there.
But at least get to the point where you can successfully manually make a PHP cURL request to your endpoint from your end out through your local and unique firewall first, then we can see if anything needs to be tweaked in the wsclient package to close any remaining gap that may remain.
It's a bit hard to debug your internal network telepathically, as you can imagine.

Comment #5

noelcusc CreditAttribution: noelcusc commented 3 February 2015 at 13:04

We use form based authentication so I cannot use the proxy settings. I'm going to see if the engineers can make an exception for this server so I wouldn't need to authenticate to access the internet.