Actions
Bug #7025
closedwebsocket: wrong value for opcode ping/pong
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
Updated by Philippe Antoine 4 months ago
- Status changed from New to In Review
Updated by Philippe Antoine 4 months ago
- Related to Feature #2695: websocket support added
Updated by Philippe Antoine 4 months ago
- Status changed from In Review to Closed
Actions