fix(client): use wss:// when served over HTTPS

[acooks]

Problem

The WebSocket URI scheme is hardcoded to ws:// in html5-client/src/js/jittertrap.js:

const wsUri = "ws://" + document.domain + ":" + location.port;

When the client is served over HTTPS, the browser blocks this as mixed content (an insecure ws:// socket from a secure page), so the live-data websocket never connects.

Fix

Derive the scheme from location.protocol, and only append a port when one is present:

const wsUri = (location.protocol === "https:" ? "wss://" : "ws://")
              + document.domain
              + (location.port ? ":" + location.port : "");

• wss:// on HTTPS pages, ws:// otherwise.
• Omitting an empty port lets it work behind a TLS-terminating reverse proxy on the default 443 (where location.port is "").

Testing

Verified on a live deployment behind nginx (TLS termination → proxy_pass to jt-server): the page loads over HTTPS and the websocket upgrade completes (101 Switching Protocols over wss://). Plain-HTTP behaviour is unchanged.

🤖 Generated with Claude Code