HTTPs secure communication between web browser and server
HTTPs (Hypertext Transfer Protocol Secure) is a secure extension of the HTTP protocol. It establishes a secure connection between a web browser and a web server, protected against eavesdropping or tampering. HTTPs can also include authentication of the remote side.
(Hypertext Transfer Protocol Secure) is a secure extension of the HTTP protocol

In the context of NETIO products

  • NETIO 4x smart socket devices can be configured over a secure connection using https (web interface).
  • For the configuration (web interface), a HTTPS port different from the HTTPS port for M2M protocols can be used; see the product configuration.
    However, in this case all M2M protocols based on HTTPS share this other port for M2M communication.
  • Some M2M APIs use HTTPS to transfer text files. This concerns in particular the REST protocols – XML and JSON. For these protocols, HTTPS is a good choice in terms of security and standards.
  • HTTPS is also used by the M2M URL API, which is a simple protocol to switch socket states by accessing a URL e.g. from a web browser.

NETIO smart sockets and PDUs use HTTPs as an extension of HTTP. It can be enabled for the web-based user interface, as well as for M2M APIs such as XML, JSON and others.

 

Certificate

NETIO devices use a certificate generated for HTTPs on the device (self signed). This method is safe against communication disruption (man in the middle).

It is not possible to save a customer certificate to a NETIO device in the regular version of the product. We do not recommend using customer certificates because they will expire one day and at that point the system will stop working.

 

Ask for a price or technical parameters

For device testing use name/password demo/demo