-
Notifications
You must be signed in to change notification settings - Fork 5.5k
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
updated Websocket in Chrome/Chromium #385
Comments
I made a pull request for a quickfix, but from what i can tell the ver 8 connection handler does not even support wss |
markvoorhies
pushed a commit
to markvoorhies/ipython
that referenced
this issue
Dec 3, 2013
We're just applying manually a fix from Tornado itself, see for details: tornadoweb/tornado#385 tornadoweb/tornado@84d7b458f956727c3b0d6710
mattvonrocketstein
pushed a commit
to mattvonrocketstein/ipython
that referenced
this issue
Nov 3, 2014
We're just applying manually a fix from Tornado itself, see for details: tornadoweb/tornado#385 tornadoweb/tornado@84d7b458f956727c3b0d6710
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I run Chrome dev channel, which has updated its websocket version, breaking compatibility with tornado websockets.
ref: http://updates.html5rocks.com/2011/10/WebSockets-updated-to-latest-version-in-Chrome-Canary
Which suggests Sec-WebSocket-Version is now 13, but Wikipedia suggests Chromium is using something called hybi 17, which may or may not be the same.
I imagine you guys are more familiar with what these things actually mean than I am.
The text was updated successfully, but these errors were encountered: