How to test the simple-websocket-server with the client about simple-websocket-server

[eidheim]

What OS are you on, and what is the output of running ws_examples?

[rragu]

I'm using centOS 6.7 64bit

[bboubaker91]

did you check your firewall policy? maybe your system is blocking the connection. did you try to stop your firewall?

[rragu]

When we run the ws_examples the port gets listened but we could not connect the server . we suspect whether there is no incoming connection or the callback handler is not working (read_handshake)
acceptor.async_accept(*connection->socket, [this, connection](const boost::system::error_code& ec) {
//Immediately start accepting a new connection
accept();
if(!ec)
{
read_handshake(connection);
}
});
There is no firewall blocking in our end,We are using BOOST_LIB_VERSION "1_59.
Your help would be highly appreciated.

Thanks in advance

[eidheim]

What client are you using?

[rragu]

We are using 2 URL's to connect server. Please find below:
chrome-extension://pfdhoblngboilpfeibdedpjgfnlcodoo/index.html
https://www.websocket.org/echo.html

[eidheim]

Check the console messages on your browser. I got:

The page at 'https://www.websocket.org/echo.html' was loaded over HTTPS, but attempted to connect to the insecure WebSocket endpoint 'ws://..../echo?encoding=text'. This request has been blocked; this endpoint must be available over WSS.doConnect @ echo.js:111
echo.js:111 Uncaught SecurityError: Failed to construct 'WebSocket': An insecure WebSocket connection may not be initiated from a page loaded over HTTPS.

When loading the page with http instead (http://www.websocket.org/echo.html) I got:

WebSocket connection to 'ws://....:8080/echo?encoding=text' failed: Connection closed before receiving a handshake response

Because of the trailing ?encoding=text I changed the endpoint in ws_examples.cpp to this and it worked:

auto& echo=server.endpoint["^/echo/?.*$"];

[rragu]

Hi Eidheim,

Great thanks for your help. It works fine now.

But can you help us to connect the server with(ws://...:8080) not with(ws://...:8080/echo?encoding=text). Is there any possibilities to run like this?

[eidheim]

That depends on the client, and here you are on your own:) Good luck!