{"id":27,"date":"2016-05-06T08:48:35","date_gmt":"2016-05-06T08:48:35","guid":{"rendered":"http:\/\/symbioticindia.in\/docu\/?p=27"},"modified":"2016-05-06T08:48:35","modified_gmt":"2016-05-06T08:48:35","slug":"nusoap-http-authentication-and-http-proxy","status":"publish","type":"post","link":"http:\/\/symbioticindia.in\/docu\/2016\/05\/06\/nusoap-http-authentication-and-http-proxy\/","title":{"rendered":"NuSOAP, HTTP Authentication and HTTP Proxy"},"content":{"rendered":"
NuSOAP and HTTP Authentication<\/strong>
\n<\/span><\/div>\n

\u00a0<\/span><\/p>\n


\n<\/span>I regularly receive emails from\u00a0 friends messing around with nusoap asking about various features of the library. Most doubts are about HTTP Authentication and\u00a0 HTTP Proxy. Here are my five cents to try and help.<\/p>\n

If your webservice server requires http authentication don’t worry, nusoap includes the method you need : “setCredentials”. Here is an example of the simplest case:<\/p>\n

$soapclient = new soapclient(“http:\/\/myserver\/mysoapservice.php”);
\n$soapclient->setCredentials(“user”,”password”);<\/p>\n

I said “the simplest case” because “setCredentials” is much more complete than this. In this case we are supposing a “Basic Authentication Type” (the one that, when set on an http page, pops up a dialog asking for a user\/password pair).We set the
\nused authentication type with the third parameter of setCredentials, and it can be: “basic”,”digest” or “certificate”, but being “basic” the default we’ve omitted it here. When we input our username and password, their “username:password” form gets
\nbase64 encoded and sent to the server as part of the headers.
\nBasic Authentication Type uses clear data(base64 is just a content transfer encoding scheme) and is therefore insecure. There are two more http authentication types we can rely on :<\/p>\n

<\/span><\/p>\n