Configuring the proxy to properly forward WebSocket requests was needed before 17.4.0, as proven by this thread Realtime WYSIWYG behind reverse proxy that is 2 years old, if you wanted to use realtime. The users that have complained were not using realtime editing before upgrading. The change between 17.4.0 and 17.4.2 is that we’re now waiting for the realtime connection to be established before allowing the user to edit. Normally, failing to connect to the realtime WebSocket end-point should fall back to editing alone (outside realtime), BUT the problem is that the bad WebSocket request forwarded by the HTTP proxy in front of XWiki is not seen as a failed request.. The browser (i.e. the JavaScript code) appears to connect and quickly disconnect to the WebSocket end-point, which leads to an indefinite number of retries. I reported Loading... .
1 Like