HTTPs details - Revision history

Tbezstarosta at 08:42, 13 August 2025

2025-08-13T08:42:19Z

Tbezstarosta at 08:41, 13 August 2025

2025-08-13T08:41:32Z

Tbezstarosta at 08:39, 13 August 2025

2025-08-13T08:39:37Z

Tbezstarosta at 08:34, 13 August 2025

2025-08-13T08:34:40Z

Tbezstarosta at 08:32, 13 August 2025

2025-08-13T08:32:37Z

Tbezstarosta at 08:30, 13 August 2025

2025-08-13T08:30:08Z

Tbezstarosta at 12:16, 11 August 2025

2025-08-11T12:16:43Z

Tbezstarosta at 12:16, 11 August 2025

2025-08-11T12:16:15Z

Tbezstarosta at 12:08, 11 August 2025

2025-08-11T12:08:42Z

Tbezstarosta at 11:57, 11 August 2025

2025-08-11T11:57:53Z

@@ Line 162: / Line 162: @@
 <b> API Performance testing </b>
 <br/>
-In internal NETIO testing on PowerPDU 4KS device (see below), various cipher suites and elliptic curves were evaluated for performance during secure HTTPS communication with the JSON and WebSocket APIs. Prime256v1 (NIST P-256) is recommended for best performance and compatibility.
+In internal NETIO testing on PowerPDU 4KS device (see below), various cipher suites and elliptic curves were evaluated for performance during secure HTTPS communication with the JSON and WebSocket APIs.

← Older revision		Revision as of 08:41, 13 August 2025
Line 161:		Line 161:

	<b> API Performance testing </b>		<b> API Performance testing </b>
		+	<br/>
	In internal NETIO testing on PowerPDU 4KS device (see below), various cipher suites and elliptic curves were evaluated for performance during secure HTTPS communication with the JSON and WebSocket APIs. Prime256v1 (NIST P-256) is recommended for best performance and compatibility.		In internal NETIO testing on PowerPDU 4KS device (see below), various cipher suites and elliptic curves were evaluated for performance during secure HTTPS communication with the JSON and WebSocket APIs. Prime256v1 (NIST P-256) is recommended for best performance and compatibility.

@@ Line 7: / Line 7: @@
 <br />
 <h2>How to enable HTTPs on NETIO Device</h2>
-All NETIO devices running on <b><u>FW 5.0.X</b></u> can be configure the way to support HTTPs communication. HTTPs option is available via Setting/ Security. Port 443 is pre-defined, but can be changed. HTTPs configuration port is shared to the port at M2M API Machine protocols setup NETIO devices support HTTPs using a self-signed certificate by default. This allows you to use secure connections immediately, even in isolated or internal networks. For production environments or public access, it is recommended to upload a certificate from a trusted Certificate Authority (CA). This ensures proper validation and avoids browser or client warnings.
+All NETIO devices running on <b><u>FW 5.0.X</b></u> can be configure the way to support HTTPs communication. HTTPs option is available via Setting/ Security. Port 443 is pre-defined, but can be changed. HTTPs configuration port is shared with M2M API protocols setup. NETIO devices support HTTPs using a self-signed certificate by default. This allows you to use secure connections immediately, even in isolated or internal networks. For production environments or public access, is recommended to upload a certificate from a trusted Certificate Authority (CA). This ensures proper validation and avoids browser or client warnings.
 <br />

@@ Line 44: / Line 44: @@
-List on combinations tested with NETIO device
+List of combinations tested with NETIO device
 <table style="border-collapse: collapse; width: 97.80949%;" border="1">
 <tr>

@@ Line 22: / Line 22: @@
 **TLS 1.0 and TLS 1.1 – (Deprecated for security reasons)
-**TLS 1.2 (Supported) (minimum secure standard and should always be used).Legacy TLS versions are disabled by default for security.
+**TLS 1.2 (<b>Supported</b>) (minimum secure standard and should always be used).Legacy TLS versions are disabled by default for security.
 **TLS 1.3 – Not supported at the moment* (future development under investigation)

@@ Line 10: / Line 10: @@
 <br />
-****ADD PICTURE
+[[File:NETIO_4PZ_HTTPs.png |Https setup]]
 <br />

@@ Line 164: / Line 164: @@
 <table border="1" cellspacing="0" cellpadding="5">
 <tr>
 <th>&nbsp;</th>
@@ Line 239: / Line 238: @@
 <td style="text-align: center;">6.5</td>
 </tr>
 </table>
 <p>* values are valid for ethernet connection only<br />
 <p>** values can differentiate on WiFi connection</p>

@@ Line 148: / Line 148: @@
 <b>Here is an examples of turning socket 1 ON using the JSON API over HTTPS:</b>
 <br />
-curl -k netio_user:netio_password -d '{"Outputs":[{"ID":1,"Action":1}]}' -H "Content-Type: application/json" -X POST https://192.168.105.160:81/netio.json
+<em>curl -k netio_user:netio_password -d '{"Outputs":[{"ID":1,"Action":1}]}' -H "Content-Type: application/json" -X POST https://192.168.105.160:81/netio.json</em>
 <br />
 **(**Replace netio_user & netio_password with proper JSON API password)
@@ Line 155: / Line 155: @@
 <b>Here is an example of turning socket 1 ON using URL over HTTPS:</b>
 <br />
-https://192.168.1.100/netio.json?pass=netio123&output1=1"
+<em>https://192.168.1.100/netio.json?pass=netio123&output1=1"</em>
 <br />
 **(**Replace netio123 with your actual API password)

@@ Line 163: / Line 163: @@
 In internal NETIO testing on PowerPDU 4KS device (see below), various cipher suites and elliptic curves were evaluated for performance during secure HTTPS communication with the JSON and WebSocket APIs. Prime256v1 (NIST P-256) is recommended for best performance and compatibility.
-<table border="1" cellpadding="5" cellspacing="0">
+<table border="1" cellspacing="0" cellpadding="5">
-  <tr>
+<tbody>
-    <th></th>
+<tr>
-    <th>Response time Web Socket [s]</th>
+<th>&nbsp;</th>
-    <th>Response time JSON [s]</th>
+<th>Response time Web Socket [s]</th>
-  </tr>
+<th>Response time JSON [s]</th>
-  <tr>
+</tr>
-    <td colspan="3"><b>ecc_prime256v1</b></td>
+<tr>
-  </tr>
+<td colspan="3"><strong>ecc_prime256v1</strong></td>
-  <tr>
+</tr>
-    <td>TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384</td>
+<tr>
-    <td>5.7</td>
+<td>TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384</td>
-    <td>6.0</td>
+<td style="text-align: center;">5.7</td>
-  </tr>
+<td style="text-align: center;">6.0</td>
-  <tr>
+</tr>
-    <td>TLS_ECDHE_ECDSA_WITH_AES_256_CCM</td>
+<tr>
-    <td>5.9</td>
+<td>TLS_ECDHE_ECDSA_WITH_AES_256_CCM</td>
-    <td>5.6</td>
+<td style="text-align: center;">5.9</td>
-  </tr>
+<td style="text-align: center;">5.6</td>
-  <tr>
+</tr>
-    <td>TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256</td>
+<tr>
-    <td>5.8</td>
+<td>TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256</td>
-    <td>5.7</td>
+<td style="text-align: center;">5.8</td>
-  </tr>
+<td style="text-align: center;">5.7</td>
-  <tr>
+</tr>
-    <td>TLS_ECDHE_ECDSA_WITH_AES_128_CCM</td>
+<tr>
-    <td>6.1</td>
+<td>TLS_ECDHE_ECDSA_WITH_AES_128_CCM</td>
-    <td>6.2</td>
+<td style="text-align: center;">6.1</td>
-  </tr>
+<td style="text-align: center;">6.2</td>
-  <tr>
+</tr>
-    <td colspan="3"><b>ecc_secp384r1</b></td>
+<tr>
-  </tr>
+<td colspan="3"><strong>ecc_secp384r1</strong></td>
-  <tr>
+</tr>
-    <td>TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384</td>
+<tr>
-    <td>6.4</td>
+<td>TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384</td>
-    <td>6.3</td>
+<td style="text-align: center;">6.4</td>
-  </tr>
+<td style="text-align: center;">6.3</td>
-  <tr>
+</tr>
-    <td>TLS_ECDHE_ECDSA_WITH_AES_256_CCM</td>
+<tr>
-    <td>6.3</td>
+<td>TLS_ECDHE_ECDSA_WITH_AES_256_CCM</td>
-    <td>6.2</td>
+<td style="text-align: center;">6.3</td>
-  </tr>
+<td style="text-align: center;">6.2</td>
-  <tr>
+</tr>
-    <td>TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256</td>
+<tr>
-    <td>6.2</td>
+<td>TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256</td>
-    <td>6.2</td>
+<td style="text-align: center;">6.2</td>
-  </tr>
+<td style="text-align: center;">6.2</td>
-  <tr>
+</tr>
-    <td>TLS_ECDHE_ECDSA_WITH_AES_128_CCM</td>
+<tr>
-    <td>6.5</td>
+<td>TLS_ECDHE_ECDSA_WITH_AES_128_CCM</td>
-    <td>6.3</td>
+<td style="text-align: center;">6.5</td>
-  </tr>
+<td style="text-align: center;">6.3</td>
-  <tr>
+</tr>
-    <td colspan="3"><b>ecc_secp521r1</b></td>
+<tr>
-  </tr>
+<td colspan="3"><strong>ecc_secp521r1</strong></td>
-  <tr>
+</tr>
-    <td>TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384</td>
+<tr>
-    <td>6.5</td>
+<td>TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384</td>
-    <td>6.4</td>
+<td style="text-align: center;">6.5</td>
-  </tr>
+<td style="text-align: center;">6.4</td>
-  <tr>
+</tr>
-    <td>TLS_ECDHE_ECDSA_WITH_AES_256_CCM</td>
+<tr>
-    <td>6.6</td>
+<td>TLS_ECDHE_ECDSA_WITH_AES_256_CCM</td>
-    <td>6.5</td>
+<td style="text-align: center;">6.6</td>
-  </tr>
+<td style="text-align: center;">6.5</td>
-  <tr>
+</tr>
-    <td>TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256</td>
+<tr>
-    <td>6.7</td>
+<td>TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256</td>
-    <td>6.3</td>
+<td style="text-align: center;">6.7</td>
-  </tr>
+<td style="text-align: center;">6.3</td>
-  <tr>
+</tr>
-    <td>TLS_ECDHE_ECDSA_WITH_AES_128_CCM</td>
+<tr>
-    <td>6.6</td>
+<td>TLS_ECDHE_ECDSA_WITH_AES_128_CCM</td>
-    <td>6.5</td>
+<td style="text-align: center;">6.6</td>
-  </tr>
+<td style="text-align: center;">6.5</td>
 </table>
-<p>* values are valid for ethernet connection only<br>
+<p>* values are valid for ethernet connection only<br />
-** values can differentiate on WiFi connection</p>
+<p>** values can differentiate on WiFi connection</p>