-
Notifications
You must be signed in to change notification settings - Fork 63
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
Connect from browsers? #32
Comments
Check the chrome://net-internal logs to get more details on the error. Note that the server has to run with TLS (and negotiate h2 or h2-14). Also, Chrome is very strict about security errors.. it won't negotiate h2 if there are certificate errors or if the negotiated ciphers don't match what the h2 specs mandates. |
Thanks for the quick reply! I find this event at Events tag as you suggested: The error seems be caused by failing to negotiate handshake and the server sent nothing to the browser. I start the server by simply "ruby server.rb" and the browser with "http://url:8080". If I load the page by "https://url:8080", the log is different: But the server still reports "HTTP2::Error::HandshakeError". So any insight to start the server with other options or get more logs from Chrome? (I'm a newbie in chrome log and am sorry if I didn't get the log in a right way.) |
|
Hello,
The ruby server and client works for me well. Now I'm wondering whether the ruby server can be connected by the browsers? When trying to do that, I always get the following log at server side:
New TCP connection!
Exception: HTTP2::Error::HandshakeError, HTTP2::Error::HandshakeError - closing socket.
which means the browser may not support the protocol. I'm using the latest Chrome on OSX.
Any idea to load the page on browser (maybe not Chrome)?
Many thanks!
The text was updated successfully, but these errors were encountered: