#Test tls 1.2 connections in curl code
I've needed to support connections to HTTPS in the past, and just went looking at old initialization code I wrote (about seven years back, how time flies). The Authorization header is an authorization Token that is provided by the InfluxDB platform that allows me to push data to it via HTTP. See below for how I am initializing the HTTP handle.
#Test tls 1.2 connections in curl update
I also learned through other forums that TLS has been in incorporated into the native LabVIEW TCP functions, but I was hoping to not have to (1) update LabVIEW, and (2) write my own HTTP functions from the TCP protocols when the HTTP Client VIs get me 95% there. So I thought I would ask if it's the HTTP Client VIs that don't support it and that should buckle down to learn the. And I shouldn't need any client certificate or private key since the server is not authenticating the client. I believe I have the proper CA certificate (a ".cer" file) for it (though this is something I'm having a hard time verifying). However the InfluxDB server requires TLS 1.2 encryption or higher and I'm presently getting a "HTTP/1.1 400 Bad Request" response when I try to POST data to it. Recently we relocated the database to a remote server (instead of local to the machine) so now I need to use HTTPS (which I understand is fine for the HTTP Client VIs).
This was working all very well and good when the database was hosted locally on the machine that was also doing the DAQ, and we were able to just use HTTP, not HTTPS. In my project I'm logging data to an InfluxDB database via http protocols. Does this also support TLS 1.2, as opposed to just SSL? This is for LabVIEW 2019
For the LabVIEW HTTP Client VIs, there is a "ConfigSSL.vi" where we are able to give it CA certification, key information, etc for security.
0 kommentar(er)
