The HTTP data POST is useful on a local network. We would like to use it over a public network using HTTPS.
I can get HTTPS working, but would like to add a single Basic Authentication Header to the POST so that the remote system can verify that the device should have access.
Is it possible to add a hardcoded Authorization Header to the HTTP export functionality?
If we add this, it would affect a lot of our customers who use this device to upload data to their server by http/https.
They need to change their server code to adapt to new batch products..
Or course, this is not the key reason.
Honestly speaking, we do not think adding basic auth would help secure a lot.
When there is basic auth, the web server will check the header "Authorization", if the check fail, the web server would reject it.
Even if there is no basic auth, you can check the SN in data, if the SN is not valid, you can also reject it.
The difference is whether this judgment is done by a web server or your code, I do not think there is too much difference
@stevenshape how did you get HTTPS to work? When I choose mode as HTTP, then the colon in the URL is stripped out when I save, and it does not work. Choosing TCP with protocol TLS also does not work.
Please refer to https://www.iammeter.com/newsshow/blog-fw-features#http-or-https