-
Notifications
You must be signed in to change notification settings - Fork 92
support websockets #15
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
Great thought, I will need to look into WSS a bit more. Since WSS is just the websockets protocol over TLS (also on port 443 by default), I think the TLS handshake part should be the same. I'll need to look into the other differences specific to the websockets protocol. Would you be interested in a potential contribution or discussion here? |
I guess Home-Assistant doesn't work with this proxy because of lack of websockets support. |
This seems to have been fixed in the golang reverse proxy since Golang 1.12 |
Should I close this issue then? |
I'm not sure which version the latest release is compiled with since I had to compile it myself (running on ARM) |
@lindell thanks for the tip! I went ahead and re-released the prebuilt binaries built using Go 1.13.3 here: https://github.com/suyashkumar/ssl-proxy/releases so all should be good on the websockets front! |
I would love to see a support for websockets.
The text was updated successfully, but these errors were encountered: