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

onerror: (-15): Remote web server responded with bad HTTP status during handshake #9

Open
zeropoid opened this issue Jul 21, 2017 · 1 comment

Comments

@zeropoid
Copy link

Getting this error. How to fix it, if I am connecting to valid wss:// host?

@savethebeesandseeds
Copy link

This also happen to me, the server response was:


HTTP/1.1 400 Bad Request
Date: Thu, 14 Apr 2022 23:14:31 GMT
Content-Type: text/plain
Content-Length: 20
Connection: keep-alive

Invalid request path


The error was self describing "invalid request path".
You are connecting to a valid ws server but given the wrong path.


My case I was trying to connect to binance:
wsclient *client = libwsclient_new("wss://stream.binance.com:9443");
but i was giving the wrong path, it work when I used instead:
wsclient *client = libwsclient_new("wss://stream.binance.com:9443/ws");


Hope this serves,
libwsclient works fine, is path specification problem.

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

2 participants