The vendor has published 1 unique mention(s) for this bug: 1. In a rare scenario where the frontend uses HTTP/2 and the backend uses HTTP/1.1, a WebSocket request might fail, causing the browser page to freeze. This issue occurs when the backend service fails to upgrade a WebSocket request from the NetScaler backend and instead sends a 200 OK status code. NetScaler then incorrectly interprets the 200 OK status as a successful response for the HTTP/2 stream on the frontend. Modules: 1. System Latest urls for this bug: 1. https://docs.netscaler.com/en-us/updates?product=NetScaler%20ADC%20%28includes%20NetScaler%20Gateway%29&version=13.1&build=58.32 2. https://docs.netscaler.com/en-us/updates?product=NetScaler%20ADC%20%28includes%20NetScaler%20Gateway%29&version=14.1&build=43.56