Skip to content
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

js websocket will take error: failed: Invalid frame header #1

Open
Leadrive opened this issue Dec 13, 2020 · 3 comments
Open

js websocket will take error: failed: Invalid frame header #1

Leadrive opened this issue Dec 13, 2020 · 3 comments

Comments

@Leadrive
Copy link

Hi,
If I use your ws-to-tcp as a nats server.
and run nats-streaming-client to test it, it is ok.

And if I use a js client to connect the ws-to-tcp, it will cause error: failed: Invalid frame header.
this js demo work ok with ws-to-relay
React demo: https://github.com/ncherro/nats-docker-ws-react
https://github.com/isobit/websocket-nats
https://github.com/isobit/ws-tcp-relay

@blinkinglight
Copy link
Owner

hey,
whole idea of this proxy to run it behind "nginx" as reverse proxy for golang programs. ( make all services reachable via http/s ports )
but now as far as know, nats.io has its own ws support which works with javascript libraries.

@Leadrive
Copy link
Author

Yes, the newest nats-server support ws.
But the nats go client does not support now.

@gedw99
Copy link

gedw99 commented Oct 20, 2021

Hey all

https://github.com/ripienaar/nats-roundtripper Supports nats Jetstream and runs embedded with caddy ( if you want ).

I am currently looking to get the nats web sockets working with it and looking for collaboration

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants