Validate WebSocket handshake keys - #105
Closed
OskarEichler wants to merge 1 commit into
Closed
Conversation
Author
|
Closing this because the changes were produced with assistance from an LLM agent, which the Faye project does not accept. Sorry for the noise. |
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Validate that Sec-WebSocket-Key is strict Base64 decoding to exactly 16 bytes before accepting a server handshake, matching RFC 6455 section 4.2.1. Malformed values currently receive a 101 response. The full 196-example suite passes on Ruby 4.0.6 and Ruby 3.2.11, as do the cumulative protocol model and native builds.