socket.io-client-cpp
socket.io-client-cpp copied to clipboard
Invalid HTTP Status
Websocketpp is failing with Invalid HTTP Status...
Did you resolve this issue? I am getting the same error for some days now...
[2017-10-04 18:46:23] [connect] Successful connection
[2017-10-04 18:46:23] [error] Server handshake response error: websocketpp.processor:20 (Invalid HTTP status.)
Connection failed.
Reconnect for attempt:4
Yes I did, I had to make some changes to allow for https connections.
I ended up resolving this issue by using a different underlying service for my server socketio implementation: Instead of using gevent which relies on long-polling, I now use eventlet which additionally supports websocket transport and allows for communication with this client out of the box.
@jammerxd care to share your changes?
Sure, give me a day or 2.
@aolivier I uploaded my mods to this repo: https://github.com/jammerxd/secure-socket.io-client-cpp
Soooo is this still open? Currently seeing this same error in my application and cant seem to get past it. Relevant stack trace:
proxy_1 | [2018-06-13 19:33:54] [connect] successful connection
proxy_1 | [2018-06-13 19:33:54] [error] server handshake response error: websocketpp.processor:20 (invalid http status.)
proxy_1 | [2018-06-13 19:33:59] [connect] successful connection
Me as well, looks like it is still an issue:
Jun 13 16:45:24 medrc-recorder-1 recorder[19546]: [2018-06-13 16:45:24] [connect] Successful connection
Jun 13 16:45:24 medrc-recorder-1 recorder[19546]: [2018-06-13 16:45:24] [error] Server handshake response error: websocketpp.processor:20 (Invalid HTTP status.)
Jun 13 16:45:24 medrc-recorder-1 recorder[19546]: [2018-06-13 16:45:24] [application] on_fail: WebSocket Connection failed, stopping telemetry!
Jun 13 16:45:24 medrc-recorder-1 recorder[19546]: [2018-06-13 16:45:24] [application] on_fail: Will try to reconnect in: 19
Did any one got how to resolve this issue?
Maybe just try the tls
branch? I'll check it in a day.
Any news on the issue?
Any updates ?
Hi guys , Any updates on this ?
I thought I found the issue was because I was trying to go with wss;//
for me issue was the tls version was wrong as this library is not upto date + there was no way to add path . I change the codebase and it worked . cheers
I still have this problem. What was the change that fixed it? Any links?
@jammerxd I also meet this issue.when I connect to a wss server without nginx,it works;but when I connect a wss server with nginx,it doesn't work! why?
any updates about this?
I encountered the same problem and resolved it by appending "/" to the resource path:
https://somehost/somepath -> https://somehost/somepath/
Using vcpkg, just install openssl-windows, then compile the project with tls version sioclient.lib.
If you use visual studio, set properties => vcpkg => Use Static Libraries
to yes. libcrypto.dll and libssl.dll will be created when the project is compiled.
But now I am wondering why I set the property to no, tls does not work properly.