From 8b585b9b020e635c4cf487a6e7808329b77c3ece Mon Sep 17 00:00:00 2001 From: BoulderBadgeDad Date: Wed, 3 Jun 2026 21:07:40 -0700 Subject: [PATCH] PR #783 follow-up: revert Socket.IO to polling-first transport PR #783 reordered transports to websocket-first for faster connects. Reverting to the polling-first default: it's the most compatible behind reverse proxies that don't forward WebSocket upgrade headers (common self-hosted setups), where websocket-first silently breaks real-time updates. The connect-time gain isn't worth the connectivity risk. Everything else from #783 (scroll-pause, content- visibility, dashboard parallelization, settings fixes, reduce-effects) kept. --- webui/static/core.js | 6 +++++- 1 file changed, 5 insertions(+), 1 deletion(-) diff --git a/webui/static/core.js b/webui/static/core.js index c6f147b7..48843c3e 100644 --- a/webui/static/core.js +++ b/webui/static/core.js @@ -382,7 +382,11 @@ function initializeWebSocket() { } socket = io({ - transports: ['websocket', 'polling'], + // Polling-first (Socket.IO default) then upgrade — most compatible behind + // reverse proxies that don't cleanly forward WebSocket upgrade headers + // (common in self-hosted setups). websocket-first shaves connect time when + // it works but silently breaks real-time updates where the proxy blocks WS. + transports: ['polling', 'websocket'], reconnection: true, reconnectionAttempts: Infinity, reconnectionDelay: 1000,