HTTP client and self signed certificates

Are there known issues with self-signed certificates and the HTTP client? I found a Vizio SmartCast API that I’m trying to create a plug-in for a SoundBar so that I can get discrete On/Off commands and feedbacks. I have verified through curl (windows command line) and postman but when I try with both the designer and app I get an error “No public methods with the specified arguments were found.” I can see the traffic in Wireshark (error below) (URL hardcoded below while troubleshooting)

   functionURL = mediaCommandURLMappings["PowerMode"]
   var url  =baseURL + functionURL
var Headers = {'Content-Type':'application/json',
		'Content-Length': url.length }  

    console.log("  URL... https://"+ host + ":" + port + functionURL);
    //response =
    try {
    response = http.get("https://10.37.250.60:9000/state/device/power_mode" );       

    sleep(250);     // sleep briefly just to make sure we get the whole response
    
    //response = response.trim();
    console.log("GetStatus called..." + response);
    } catch (error) {
        console.log(error);
    }

WireShark:
Frame 610: 54 bytes on wire (432 bits), 54 bytes captured (432 bits) on interface \Device\NPF_{B472FDBE-BB7D-4CCE-A514-24B6D8C7B09E}, id 0
Ethernet II, Src: ASUSTekC_d2:93:a6 (2c:4d:54:d2:93:a6), Dst: IOGEAR_c7:03:6e (00:21:79:c7:03:6e)
Internet Protocol Version 4, Src: 10.37.250.121, Dst: 10.37.250.60
0100 … = Version: 4
… 0101 = Header Length: 20 bytes (5)
Differentiated Services Field: 0x00 (DSCP: CS0, ECN: Not-ECT)
Total Length: 40
Identification: 0xd463 (54371)
Flags: 0x40, Don’t fragment
Fragment Offset: 0
Time to Live: 128
Protocol: TCP (6)
Header Checksum: 0x0000 [validation disabled]
[Header checksum status: Unverified]
Source Address: 10.37.250.121
Destination Address: 10.37.250.60
Transmission Control Protocol, Src Port: 53249, Dst Port: 9000, Seq: 312, Ack: 2621, Len: 0
Source Port: 53249
Destination Port: 9000
[Stream index: 22]
[TCP Segment Len: 0]
Sequence Number: 312 (relative sequence number)
Sequence Number (raw): 1911173279
[Next Sequence Number: 312 (relative sequence number)]
Acknowledgment Number: 2621 (relative ack number)
Acknowledgment number (raw): 861489835
0101 … = Header Length: 20 bytes (5)
Flags: 0x014 (RST, ACK)
000. … … = Reserved: Not set
…0 … … = Nonce: Not set
… 0… … = Congestion Window Reduced (CWR): Not set
… .0… … = ECN-Echo: Not set
… …0. … = Urgent: Not set
… …1 … = Acknowledgment: Set
… … 0… = Push: Not set
… … .1… = Reset: Set
[Expert Info (Warning/Sequence): Connection reset (RST)]
[Connection reset (RST)]
[Severity level: Warning]
[Group: Sequence]
… … …0. = Syn: Not set
… … …0 = Fin: Not set
[TCP Flags: ·······A·R··]
Window: 0
[Calculated window size: 0]
[Window size scaling factor: 256]
Checksum: 0x091b [unverified]
[Checksum Status: Unverified]
Urgent Pointer: 0
[SEQ/ACK analysis]
[Timestamps]

Yes, you probably will have issues with self-signed certificates when using Plugins. In the next release 4.2.1, I will update the Plugin’s HTTPClient to ignore certificate errors for HTTPS.

Thanks, Will put it on hold until then.