Yes, Lua can call HTTPS, but you have to properly configure Orthanc.
In the configuration file [1], carefully read the “HttpsVerifyPeers” and “HttpsCACertificates” options.
Please also note that as of Orthanc 1.0.0, you cannot connect against self-signed HTTPS certificates, even if “HttpsVerifyPeers” is set to “false”. This issue is now fixed in the mainline, and the fix will be part of Orthanc 1.0.1.
As a follow up:
When I use Orthanc docker mainline w/ plugins (20160205T173109), with the HttpsVerifyPeers set to false, Lua script can successfully make calls to HTTPS endpoint.
However, keeping everything the same, when I use Orthanc docker mainline w/ plugins (20161118T163419), Lua script cannot make calls to HTTPS endpoint, with the following error:
libCURL error: Problem with the SSL CA cert (path? access rights?)
So, in short, when I upgrade Orthanc docker mainline (20160205T173109) to Orthanc docker mainline (20161118T163419), calling https no longer works.
When I “downgrade” the code, call https works again.
Is there an updated method to enable calling of https endpoint in place of (or in addition to) setting HttpsVerifyPeers option to false?
Attached is the configuration file used, and also sample lua script. In short, the configuration file is derived from the sample configuration from Orthanc docker mainline w/ plugins (20160205T173109), with updates to HttpsVerifyPeers, HttpsCACertificates, and postgres section added.
Additional note:
When I set HttpsVerifyPeers to true, and provide HttpsCACertificates, I am able to call HTTPS endpoint with Orthanc docker mainline w/ plugins (20160205T173109), but not when I upgrade to Orthanc docker mainline w/ plugins (20161118T163419). I continue to get the same libCURL error:
libCURL error: Problem with the SSL CA cert (path? access rights?)