Just a note (for later readers of this thread)...My experience now with this trick seems to say that, as long as "https" is in the URL, a /SSLContextService/ must be supplied. As a URL with "https" and port number 8443 is the only way I have to engage TLS at the far end, I must live with /SSLContextService/'s requirements.
On 7/26/22 19:17, Paul Grey wrote:
leave the InvokeHTTP property SSLContextService blank.
