It does not appear that any documentation is shipped around CURLLink
, and normally this means that it is unsupported by WRI. However, the source is shipped without any obfuscation and most of it is in Wolfram Language, so you can gain insight into its inner workings that way.
On my system, it seems the source code for CURLLink lives at
FileNameJoin[{$InstallationDirectory, "SystemFiles", "Links", "CURLLink"}]
From a cursory glance, CURLLink
is a wrapper around libcurl
that allows for low-level HTTP actions. More than likely it's used internally as the underpinnings of URLRequest
and friends, and it is probably undocumented because it's somewhat un-WL to have these direct wrappers to external functionality (calling libcurl to POST a HTTP form) instead of a more idiomatic interface (such as URLRequest
). It may also be undocumented because the interface is very likely to change in future releases - although I find this reason unlikely because libcurl itself is historically extremely stable.
You may find the libcurl
documentation somewhat useful in your escapades.
CURLLink
is probably a wrapper around libcurl? You could start by doingNeeds["CURLLink`"]
, then using?CURLForm
orResourceFunction["PrintDefinitions"][CURLForm]
. It does not appear than any documentation is shipped aroundCURLLink
, and normally this means that it is unsupported by WRI. $\endgroup$CURLLink
lives atFileNameJoin[{$InstallationDirectory, "SystemFiles", "Links", "CURLLink"}]
It does not appear that any documentation is included but the source is readable. $\endgroup$