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.qrc | 2 ++ 1 file changed, 2 insertions(+) (limited to 'data.qrc') diff --git a/data.qrc b/data.qrc index d44218a..bad64a5 100644 --- a/data.qrc +++ b/data.qrc @@ -16,5 +16,7 @@ data/ui/lobby_assets/down-arrow.png data/ui/lobby_assets/up-arrow.png data/ui/moderator_action_dialog.ui + data/icons/https.svg + data/icons/noencryption.svg -- cgit