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 has been archived by the owner on Dec 7, 2020. It is now read-only.
I am trying to use keyckloack-proxy as a front-end for on-premise kubernetes cluster.
Everything works, but one of the UI features, that opens a shell on the pod using web sockets.
When I try to open a shell, the connection closes after a second with the following proxy error :
Having also just hit this issue, I tried figuring out what is causing this to break. AFAICS, the issue is caused by a chimiddleware.flushWriter being used instead of a middleware.httpFancyWriter. The decision which one to use seems to happen in NewWrapResponseWriter and the exact logic depends on whether HTTP/2 is in use.
This is most likely the culprit in my setup as keycloak-proxy is running behind an nginx reverse proxy, so connections get downgraded to HTTP/1.1 and at least one of cn, hj or rf is false causing the code to fall through to the flushWriter creation.
I am trying to use keyckloack-proxy as a front-end for on-premise kubernetes cluster.
Everything works, but one of the UI features, that opens a shell on the pod using web sockets.
When I try to open a shell, the connection closes after a second with the following proxy error :
The proxy version I use:
keycloak-proxy version v2.1.0-rc5 (git+sha: no gitsha provided, built: 01-01-1970)
Is it a bug?
am I missing a flag, again? :)
The text was updated successfully, but these errors were encountered: