You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When HTTP/2 is enabled, HAProxy will attempt to bootstrap WebSocket connections via HTTP/2 as defined in RFC 8441.
Since not all backends implement RFC 8441, this can break WebSocket requests that would otherwise work with HTTP/1.1. For example, Golang's HTTP server does not yet support HTTP/2 WebSockets: golang/go#32763.
Impact to Cloud Foundry
For Cloud Foundry, enabling HTTP/2 on HAProxy will break WebSocket request to apps and streaming app logs from Loggregator. This is because the Gorouter (using Golang's HTTP server) does not support WebSockets over HTTP/2.
Possible Fix
One possible workaround would be to (optionally?) configure a separate backend for WebSocket traffic over HTTP/1.1. For example, something like:
Related Issue: cloudfoundry/routing-release#230
Root Issue
When HTTP/2 is enabled, HAProxy will attempt to bootstrap WebSocket connections via HTTP/2 as defined in RFC 8441.
Since not all backends implement RFC 8441, this can break WebSocket requests that would otherwise work with HTTP/1.1. For example, Golang's HTTP server does not yet support HTTP/2 WebSockets: golang/go#32763.
Impact to Cloud Foundry
For Cloud Foundry, enabling HTTP/2 on HAProxy will break WebSocket request to apps and streaming app logs from Loggregator. This is because the Gorouter (using Golang's HTTP server) does not support WebSockets over HTTP/2.
Possible Fix
One possible workaround would be to (optionally?) configure a separate backend for WebSocket traffic over HTTP/1.1. For example, something like:
The text was updated successfully, but these errors were encountered: