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.

Sign up for GitHub

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

Jump to bottom

Fail Connection on non-zero RSV bit #33

Closed
statianzo opened this issue Jan 18, 2012 · 0 comments
Closed

Fail Connection on non-zero RSV bit #33

statianzo opened this issue Jan 18, 2012 · 0 comments
Labels
RFC Compliance
Milestone
1.0

Comments

@statianzo
Copy link
Owner

Per Spec:

RSV1, RSV2, RSV3: 1 bit each

  MUST be 0 unless an extension is negotiated that defines meanings
  for non-zero values.  If a nonzero value is received and none of
  the negotiated extensions defines the meaning of such a nonzero
  value, the receiving endpoint MUST _Fail the WebSocket
  Connection_.
orcun pushed a commit to orcun/Fleck that referenced this issue Sep 30, 2013
@statianzo @orcun
Verify opcodes + RSV bits. fixes statianzo#33
4dc7999
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
RFC Compliance
Projects
None yet
Milestone
1.0
Development

No branches or pull requests
1 participant
@statianzo