You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
socket.io-client-cpp does not connect to node app on Heroku #221
Changed URL from https to http://myapp.heroku.com - works now. Is it possible to connect via https as well. JS socket.io-client allows this. https://stackoverflow.com/q/53736781/630169
@akontsevich I'm still trying to connect to a simple node js server hosted locally (which is using http) build using express, and implemented a simple socket.io on it. But I'm still stuck in connecting, and getting the following error.
I'm trying to run the console example app, and using VS 2017 and 141v toolset. I also pointed the submodules (rapidjson and websocketpp) to their head. Any other change I need to make?
I'm trying to run the console example app, and using VS 2017 and 141v toolset. I also pointed the submodules (rapidjson and websocketpp) to their head. Any other change I need to make?
@pampas93 also get following error today trying to connect to local node.js server:
[connect] Successful connection
[2019-09-11 16:22:31] [error] handle_transport_init received error: TLS handshake failed
[2019-09-11 16:22:31] [info] asio async_shutdown error: asio.ssl:336462231 (shutdown while in init)
cause for production I've built with DEFINES += SIO_TLS in .pro file (-DSIO_TLS compiller switch). Commented this out for now for local unsecure run.
Activity
akontsevich commentedon Dec 12, 2018
Changed URL from
httpstohttp://myapp.heroku.com - works now. Is it possible to connect via https as well. JSsocket.io-clientallows this.https://stackoverflow.com/q/53736781/630169
akontsevich commentedon Dec 12, 2018
Built app with
SIO_TLSinDEFINES(-DSIO_TLS) - connects viahttpsfine now!Solution found here: #137
pampas93 commentedon Mar 31, 2019
@akontsevich I'm still trying to connect to a simple node js server hosted locally (which is using http) build using express, and implemented a simple socket.io on it. But I'm still stuck in connecting, and getting the following error.
I'm trying to run the console example app, and using VS 2017 and 141v toolset. I also pointed the submodules (rapidjson and websocketpp) to their head. Any other change I need to make?
akontsevich commentedon Sep 11, 2019
@pampas93 also get following error today trying to connect to local
node.jsserver:cause for production I've built with
DEFINES += SIO_TLSin.profile (-DSIO_TLScompiller switch). Commented this out for now for local unsecure run.