HTTPS and HTTP/2

ClawIO runs by default on non-secured HTTP connections. If ClawIO is going to be used by multiple users or exposed to the Internet, you should secure it enabling TLS so your communications will go encrypted end-to-end.

When enabling TLS/HTTPS, ClawIO will enable support for HTTP/2, so HTTP/2-ready clients can take advantages of HTTP/2 performance.

For enabling TLS you need two files:

• The server private key in PEM format
• The server cerficate in PEM format (ideally signed by a trusted certification authority)

Once you have them, enable TLS communications in the configuration file:

{
  "server": {
    "tls_enabled": true,
    "tls_certificate": "/etc/clawiod/cert.pem",
    "tls_private_key": "/etc/clawiod/key.pem"
  }
}