Repository navigation
Close the connection on malformed binary messages - #321
Open
maximmaxim345 wants to merge 3 commits into
Open
maximmaxim345 wants to merge 3 commits into
maximmaxim345 wants to merge 3 commits into
Conversation
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.
The spec didn't say what to do with a binary message that has no message ID, a JSON message (ID
0) that isn't a valid JSON object with atypestring and apayloadobject, or a player, source or visualizer message shorter than its header.These are now protocol errors that close the connection. This follows the existing artwork rule for messages shorter than 2 bytes and the truncated fragment frames added in:
Add truncated fragment frames to malformed sequences #297
I accept the Contributor License Agreement for this contribution.