Bug 23838 - WebSocket continuation frame incorrectly handles the message type OPCODE
Summary: WebSocket continuation frame incorrectly handles the message type OPCODE
Alias: None
Product: Class Libraries
Classification: Mono
Component: System ()
Version: unspecified
Hardware: All All
: --- major
Target Milestone: Untriaged
Assignee: Bugzilla
Depends on:
Reported: 2014-10-15 08:35 UTC by Matthew Leibowitz
Modified: 2016-04-27 15:09 UTC (History)
2 users (show)

Is this bug a regression?: ---
Last known good build:

Notice (2018-05-24): bugzilla.xamarin.com is now in read-only mode.

Please join us on Visual Studio Developer Community and in the Xamarin and Mono organizations on GitHub to continue tracking issues. Bugzilla will remain available for reference in read-only mode. We will continue to work on open Bugzilla bugs, copy them to the new locations as needed for follow-up, and add the new items under Related Links.

Our sincere thanks to everyone who has contributed on this bug tracker over the years. Thanks also for your understanding as we make these adjustments and improvements for the future.

Please create a new report on GitHub or Developer Community with your current version information, steps to reproduce, and relevant error messages or log files if you are hitting an issue that looks similar to this resolved bug and you do not yet see a matching new report.

Related Links:

Description Matthew Leibowitz 2014-10-15 08:35:02 UTC
When a frame marked with OPCODE 0, it is a continuation frame. 
This frame does not carry the message type and should be derived from the previous frame.

More info on the pull - https://github.com/mono/mono/pull/1345

Some logging - https://gist.github.com/mattleibow/b7a532cb52bd7026d4ff
When a frame is encountered, if the OPCODE is 1, then it is a text message. On continuation frames, the OPCODE is 0, and does not contain the message type, such as text or binary. Thus, the message type is the same as the previous frame's message type.

See more info: http://tools.ietf.org/html/rfc6455#section-5.2
Comment 1 Alexander Köplinger [MSFT] 2016-04-27 15:09:26 UTC
Merged the PR, thanks!