A customer's app (a Golang-based WebSocket broker) suddenly started rejecting WebSockets that are being managed by ZBR.
Although the WebSocket frame data looks OK just before it is transmitted over the Ziti overlay (i.e. no RSV2/3 bits are set in the frame), the remote Service responds with a connection-close opcode, and a payload of "RSV2 set, RSV3 set, FIN not set on control, bad MASK".
Multiple WebSockets are opened in this web app, and some WebSockets run fine. Only one fails as described above, which is odd because the same ZBR code manages all WebSockets the same way.
rentallect
commented
2 months ago
A customer's app (a Golang-based WebSocket broker) suddenly started rejecting WebSockets that are being managed by ZBR.
Although the WebSocket frame data looks OK just before it is transmitted over the Ziti overlay (i.e. no RSV2/3 bits are set in the frame), the remote Service responds with a connection-close opcode, and a payload of "RSV2 set, RSV3 set, FIN not set on control, bad MASK".
Multiple WebSockets are opened in this web app, and some WebSockets run fine. Only one fails as described above, which is odd because the same ZBR code manages all WebSockets the same way.