Fix VNC WebSocket 'Invalid frame header' error
- Remove WebSocket-level chunking of VNC data (breaks streaming protocol) - Send VNC data as complete WebSocket frames instead of chunks - Enhance SSL error handling with better retry logic and exponential backoff - Make VNC handler resilient to temporary SSL buffer issues - Add comprehensive debug logging for WebSocket frame transmission - Add client-side debug logging for VNC rectangle processing Root cause: WebSocket chunking interrupted VNC TightDecoder which expects complete compressed data blocks. Client accumulated partial data until connection reset with ECONNRESET.
Showing
This diff is collapsed.
Please
register
or
sign in
to comment