From 79c2262cae02b513aee70943f7e07a9205316bdf Mon Sep 17 00:00:00 2001 From: Osmium Sorcerer Date: Sun, 22 Mar 2026 17:57:13 +0000 Subject: Support Secure WebSocket Add full WSS support to public server list (using wss_port, overriding insecure port), favorite servers list, and direct connections, and show which servers are secure. Revert the upstream's removal of `legacy` ServerInfo field, as I use it to filter out legacy servers. To differentiate schemes, the `scheme` field is used, either "ws" or "wss". I don't see the reason to add "tcp" protocol when we don't even support it. For the UI, add icons for secure and insecure connections. Highlight secure servers with a green background. In the favorite server dialog, a checkbox was added to select whether the server is using WSS. In the direct connection dialog, support "wss" scheme and default ports: 80 for WS, 443 for WSS, as per the WebSocket specification. --- data/icons/https.svg | 1 + data/icons/noencryption.svg | 1 + 2 files changed, 2 insertions(+) create mode 100644 data/icons/https.svg create mode 100644 data/icons/noencryption.svg (limited to 'data/icons') diff --git a/data/icons/https.svg b/data/icons/https.svg new file mode 100644 index 0000000..87a3c2b --- /dev/null +++ b/data/icons/https.svg @@ -0,0 +1 @@ + \ No newline at end of file diff --git a/data/icons/noencryption.svg b/data/icons/noencryption.svg new file mode 100644 index 0000000..91524c5 --- /dev/null +++ b/data/icons/noencryption.svg @@ -0,0 +1 @@ + \ No newline at end of file -- cgit