Skip to content
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

Reserved bit error #65

Open
key88sf opened this issue Jun 3, 2014 · 2 comments
Open

Reserved bit error #65

key88sf opened this issue Jun 3, 2014 · 2 comments

Comments

@key88sf
Copy link

key88sf commented Jun 3, 2014

I'm getting the following error in the chrome console when connecting with the latest Chrome browser:

One or more reserved bits are on: reserved1 = 1, reserved2 = 0, reserved3 = 0 

Is this because Cramp doesn't support the latest protocol yet? Or ??

@key88sf
Copy link
Author

key88sf commented Jun 3, 2014

Verified this error happens with all browser, and even the faye websocket client for Ruby.

@key88sf key88sf changed the title Chrome 14 reserved bit error Reserved bit error Jun 3, 2014
@chall8908
Copy link
Contributor

It's possible this problem is related to #64 and may be solved by #67

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants