RDS HTML5 WebClient - WebSocket issues on reconnection

Take this:

1. WebSocket Support in Azure App Proxy
• Confirm that WebSocket support is fully enabled in your Azure App Proxy configuration. Even if it appears to work intermittently, inconsistent behavior can stem from proxy timeouts or dropped upgrade headers.
2. Idle Timeout Settings
• Check the App Proxy connector idle timeout and RD Gateway timeout policies. If the WebSocket is idle too long, it may be dropped silently.
3. Reverse Proxy or Firewall Interference
• If you're using a reverse proxy (e.g., NGINX, NetScaler), ensure it’s configured to allow WebSocket traffic (Upgrade and Connection headers must be preserved).
• Some users resolved similar issues by adjusting Content-Security-Policy headers and allowing blob: and data: sources.
4. Client-Side Network Conditions
• Random disconnects can also be caused by unstable client networks (e.g., Wi-Fi drops, VPN latency). Consider enabling diagnostic logging on the client side to correlate disconnects with network events.
5. WebClient Version & Updates
• Make sure you're using the latest version of the HTML5 WebClient. Microsoft occasionally releases fixes that improve reconnection logic and WebSocket resilience.
6. Fallback Strategy
• If reconnection fails after 10 attempts, consider scripting a client-side refresh or auto-click of the reconnect button as a temporary workaround.