NetGain replying to Ping with OpCode.Binary
mprync opened this issue · 1 comments
mprync commented
Inside of
NetGain/StackExchange.NetGain/WebSockets/WebSocketsProcessor_RFC6455_13.cs
Is it intended for the ping to be handled with pong.OpCode = WebSocketsFrame.OpCodes.Binary;
I was getting client disconnects because ping was not being responded to with a pong.
I've changed it to OpCodes.Pong; and it works as expected. Is this a bug or is there something apart of the RFC6455 standard that I'm missing?