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
{{ message }}
This repository was archived by the owner on Mar 29, 2026. It is now read-only.
The WS config should use Ingress-domain when returning the URL. Currently when a user asks for a websocket transport, the hostname they are connecting to the server with is used to populate the WS url. This can lead to very awkward errors when using loadbalancers or reverse proxies. The WS URL should not rely on anything userspecified, but should instead be entirely derived from server config.
The WS config should use Ingress-domain when returning the URL. Currently when a user asks for a websocket transport, the hostname they are connecting to the server with is used to populate the WS url. This can lead to very awkward errors when using loadbalancers or reverse proxies. The WS URL should not rely on anything userspecified, but should instead be entirely derived from server config.