-
Notifications
You must be signed in to change notification settings - Fork 51
WebSocket Support #35
Comments
Looking at the implementation here: osiris/pkg/net/http/httputil/reverseproxy.go Lines 506 to 548 in 4f8deee
And based on this comment: golang/go#26937 (comment) I see that the implementation used relies on Go 1.12 features, where as I believe this project is complied with Go 1.11. The comment below shows an implementation which works with 1.11. |
There is no support for web sockets at the moment, nor do I believe it's planned. (This project is relatively dormant at the moment.)
Relevant Go 1.12 features were replicated in our own source tree. Now that Go 1.12 is available, we can probably undo that. |
Ah, I see that now. Makes sense.
That is sad to hear, especially with how some projects rely on websockets, but it's at least good to know. |
Environment:
helm install osiris/osiris-edge --name osiris --namespace osiris-system --devel
What happened?
I have been starting to use this project to scale down our preview environments (which is really awesome btw!). However I came across issues when I tried to use this one of our services which relies on websockets. The browser gets a '502 Bad Gateway' response from the websocket requests. Checking the logs from the proxy sidecar I see this error:
So I was wondering if websockets are supported, and what I might be missing to get this working?
What you expected to happen?
Websocket requests work correctly through the proxy.
The text was updated successfully, but these errors were encountered: