You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
My WebSocket client is frequently receiving frames with unknown frame opcodes: [oatpp::web::protocol::websocket::AsyncWebSocket::handleFrameAsync(){HandleFrameCoroutine}]: Unknown frame. I would like to be able to inspect these frame opcodes to know what the opcodes are and potentially respond to them.
The suggested solution of creating a custom implementation of listenAsync is not currently possible because it accesses private members such as readFrameHeaderAsync.
The text was updated successfully, but these errors were encountered:
My WebSocket client is frequently receiving frames with unknown frame opcodes:
[oatpp::web::protocol::websocket::AsyncWebSocket::handleFrameAsync(){HandleFrameCoroutine}]: Unknown frame
. I would like to be able to inspect these frame opcodes to know what the opcodes are and potentially respond to them.The suggested solution of creating a custom implementation of listenAsync is not currently possible because it accesses private members such as
readFrameHeaderAsync
.The text was updated successfully, but these errors were encountered: