Older versions of NetCurl was not "chained" as default. All calls made had to be separately made, instead of X->CALL()→chainedCall().
All examples on this page are based on the unit tests delivered with the module.
The module name is as the name reveals based on the curl library. But it also supports other web-drivers. Besides of this, this module has a small driver for handling basic SOAP-calls. The class itself is called Tornevall_SimpleSoap, and is initialized automatically when using http-calls with "?wsdl" in the URL. If you think that the tiny parameter "?wsdl" is useless, enforcing the SoapClient during the web-call is possible by using NETCURL_POST_DATATYPES::DATATYPE_JSON, instead of DATATYPE_JSON or similar. More about this, will come.
Deprecation of class name Tornevall_cURL
As of v6.0.20, netcurl is splitted up in sections and classes instead of having all source code in one bundled file. The name Tornevall_cURL has been renamed and is from this version deprecated. The new name of all classes is based on MODULE_<name>, meaning Tornevall_cURL is now known as MODULE_CURL. Most of the components are backwards compatible, so using for example CURL_POST_AS instead of the new class NETCURL_POST_DATATYPES still works.
The easiest way to get started with the module is with composer:
Then add a code block to your php-script:
The last usage-row is added to simplify the instance creation of the library. Instead of running
this makes it possible to just run a
Note that if you initialize the module with no constructor arguments, you can set it up more detailed afterwards. The module was, before the chain implementation, built in a way that you in a default state never needed to configure anything, but configuration was available if requirements changed. For example, it was possible to initialize the module and then run more calls after each other, with different settings (i.e. different outgoing ip-interfaces, when there was a need to spread the calls between many hosts). Yes; this is basically a "going under the radar"-function, with spoofability.
To make a call to a website, NetCurl provides some basic methods that does the hard work for you. Depending on what you need to do (GET data, POST data, etc), the methods are called following:
|doGet||GET||Goes with a simple URL|
|doPost||POST||URL, postData, postAs||Makes a POST call with including data, if provided.|
Included data can be both strings and arrays. If the data is something else than a string, NetCurl tries to translate the data into a proper format.
The format is a bit dependent on the postAs-Parameter. Default is CURL_POST_AS::POST_AS_NORMAL.
This mode will try to post data in a to-websites-proper-formatting, for example &a=standard&post=format.
|doDelete||DELETE||URL, postData, postAs||Makes a DELETE call, with including data. See POST.|
|doPut||PUT||URL, postData, postAs||Makes a PUT call, with including data. See POST.|
Quick start: Oneliners
Running with the latest version of NetCurl makes it possible to quick-fire a web-session, with only one row of code.
The response of the request should look like something like this:
With NetCurl 6.0.18 and newer versions, initializing the library with authenication values is also possible. However, currently, the best supported authentication is CURLAUTH_BASIC (NETCURL_AUTH_TYPES::AUTHTYPE_BASIC), with failover on CURLAUTH_ANY. To use authentication at construction level, one can use something like this:
Without this oneliner, the call can also be done with the following code: