Project

General

Profile

Actions

Bug #7025

closed

websocket: wrong value for opcode ping/pong

Added by Philippe Antoine about 1 month ago. Updated about 1 month ago.

Status:
Closed
Priority:
Normal
Target version:
Affected Versions:
Effort:
Difficulty:
Label:

Description

Cf https://datatracker.ietf.org/doc/html/rfc6455

   Opcode:  4 bits

      Defines the interpretation of the "Payload data".  If an unknown
      opcode is received, the receiving endpoint MUST _Fail the
      WebSocket Connection_.  The following values are defined.

      *  %x0 denotes a continuation frame

      *  %x1 denotes a text frame

      *  %x2 denotes a binary frame

      *  %x3-7 are reserved for further non-control frames

      *  %x8 denotes a connection close

      *  %x9 denotes a ping

      *  %xA denotes a pong

      *  %xB-F are reserved for further control frames

Related issues 1 (0 open1 closed)

Related to Suricata - Feature #2695: websocket supportClosedPhilippe AntoineActions
Actions #1

Updated by Philippe Antoine about 1 month ago

  • Status changed from New to In Review
Actions #2

Updated by Philippe Antoine about 1 month ago

Actions #3

Updated by Philippe Antoine about 1 month ago

  • Status changed from In Review to Closed
Actions

Also available in: Atom PDF