<pclass="level0">Returns a pointer to a filled in static struct with information about various features in the running version of libcurl. <spanClass="emphasis">type</span> should be set to the version of this functionality by the time you write your program. This way, libcurl will always return a proper struct that your program understands, while programs in the future might get a different struct. <spanClass="bold">CURLVERSION_NOW</span> will be the most recent one for the library you have installed:
<pclass="level0"> data = curl_version_info(CURLVERSION_NOW);
<pclass="level0">Applications should use this information to judge if things are possible to do or not, instead of using compile-time checks, as dynamic/DLL libraries can be changed independent of applications.
<pclass="level0">The curl_version_info_data struct looks like this
<pclass="level0"><spanClass="emphasis">age</span> describes what the age of this struct is. The number depends on how new the libcurl you're using is. You are however guaranteed to get a struct that you have a matching struct for in the header, as you tell libcurl your "age" with the input argument.
<pclass="level0"><spanClass="emphasis">version</span> is just an ascii string for the libcurl version.
<pclass="level0"><spanClass="emphasis">version_num</span> is a 24 bit number created like this: <8 bits major number> | <8 bits minor number> | <8 bits patch number>. Version 7.9.8 is therefore returned as 0x070908.
<pclass="level0"><spanClass="emphasis">host</span> is an ascii string showing what host information that this libcurl was built for. As discovered by a configure script or set by the build environment.
<pclass="level0"><spanClass="emphasis">features</span> can have none, one or more bits set, and the currently defined bits are:
<pclass="level1">libcurl was built with support for asynchronous name lookups, which allows more exact timeouts (even on Windows) and less blocking when using the multi interface. (added in 7.10.7)
<pclass="level1">libcurl was built with support for SPNEGO authentication (Simple and Protected GSS-API Negotiation Mechanism, defined in <ahref="http://www.ietf.org/rfc/rfc2478.txt">RFC 2478</a>.) (added in 7.10.8)
<pclass="level1">libcurl was built with support for SSPI. This is only available on Windows and makes libcurl use Windows-provided functions for Kerberos, NTLM, SPNEGO and Digest authentication. It also allows libcurl to use the current user credentials without the app having to pass them on. (Added in 7.13.2)
<pclass="level1">libcurl was built with support for GSS-API. This makes libcurl use provided functions for Kerberos and SPNEGO authentication. It also allows libcurl to use the current user credentials without the app having to pass them on. (Added in 7.38.0)
<pclass="level0"><spanClass="emphasis">ssl_version</span> is an ASCII string for the OpenSSL version used. If libcurl has no SSL support, this is NULL.
<pclass="level0"><spanClass="emphasis">libz_version</span> is an ASCII string (there is no numerical version). If libcurl has no libz support, this is NULL.
<pclass="level0"><spanClass="emphasis">protocols</span> is a pointer to an array of char * pointers, containing the names protocols that libcurl supports (using lowercase letters). The protocol names are the same as would be used in URLs. The array is terminated by a NULL entry. <aname="RETURN"></a><h2class="nroffsh">RETURN VALUE</h2>
<pclass="level0">A pointer to a curl_version_info_data struct. <aname="SEE"></a><h2class="nroffsh">SEE ALSO</h2>
