Skip to content

Incorrect websocket opcode for defragmented frame #287

@cpq

Description

@cpq

Context:
Fossa implementation had also a bug and did not report the correct OpCode for fragmented frames. It reports 0 (continuation frame) instead of the correct OpCode (1 or 2) contained in the first fragment.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions