Troubleshoot missing WebSocket upgrade headers

Last updated on Dec 16, 2024

Issue

Adobe logs have shown an increase in HTTP 400 errors for WebSocket endpoints in Adobe Express. The error response indicates missing Upgrade headers in client connection requests.

Enterprise clients may see these 400 responses when trying to establish WebSocket connections. This can happen when a proxy server in your enterprise environment strips or blocks the Upgrade header before the request reaches Adobe's servers.

Resolution

If your enterprise environment routes traffic through a proxy server, configure the proxy to treat the Upgrade header as hop-by-hop and pass it through unchanged on WebSocket connection requests. Stripping this header at the proxy causes the connection to fail with an HTTP 400 error.

See WebSocket proxying configuration for more details.