Minimum support for hybi13 #22
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Applied, Thanks. We should also make sure that the handling of |
|
I was wondering about that. I'm no expert, but...
So it looks like we're only wrong for draft hybi 10, but I don't know about the intermediate drafts, and if they're in use at all. On top of that, draft hixie 76 had a response header |
|
Is hybi-17 in chrome 15? |
|
Nope. Current Canary will be Chrome 16. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Chrome Canary builds are now using websocket protocol version 13, from draft-ietf-hybi-thewebsocketprotocol-17. This commit basically matches the work done in the related WebKit commit and pywebsocket commit.