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 }}
This repository has been archived by the owner on Jun 12, 2018. It is now read-only.
Excuse me, When Wss protocol work, I have an problem is that in my program doesn't work for Google Chrome browser,the error when it connect; But it can worked well in IE11, when debug I found that in goole chrome when run on read_handshake(connection), and into asio::async_read_until(*connection->socket, connection->read_buffer, "\r\n\r\n", [this, connection](const error_code &ec, size_t /bytes_transferred/) function , the connection->read_buffer haven't data, and client of Google Chrome browser Websocket in dis connected, So I was confused for this problem.
The text was updated successfully, but these errors were encountered:
When i use openssl , I found a " No ALPN negotiated " marks, https://ma.ttias.be/day-google-chrome-disables-http2-nearly-everyone-may-31st-2016/ said, Chrome 51+ doesn't support "No ALPN negotiated " service, in my program, The Chrome is 59, I don't known it may be this problem so that can't connect with Chrome? and we should how to support ALPN negotiated?
In Chrome 49 it is OK to connect, But Chrome 59 haven't connected, so it probably is ALPN in this program no't support, so How to support ALPN negotiated?
Excuse me, When Wss protocol work, I have an problem is that in my program doesn't work for Google Chrome browser,the error when it connect; But it can worked well in IE11, when debug I found that in goole chrome when run on read_handshake(connection), and into asio::async_read_until(*connection->socket, connection->read_buffer, "\r\n\r\n", [this, connection](const error_code &ec, size_t /bytes_transferred/) function , the connection->read_buffer haven't data, and client of Google Chrome browser Websocket in dis connected, So I was confused for this problem.
The text was updated successfully, but these errors were encountered: