WebSocketMessageReadRfc6455Stream.CheckBoundaries is incorrect about websocketlistener HOT 4 CLOSED

How did you reproduce this problem?

Thanks!

from websocketlistener.

Hi,
Sorry for the late reply, I had forgotten about the issue because I had already fixed it locally.
I think I ran into the issue when I did an experiment that involved first reading the first four bytes of a message, then depending on their value doing something with the rest of the message. Reading the first four bytes failed because of the aforementioned test: (4 < buffer.Length - 0) => throw exception.

So under normal circumstances, as long as you always read the entire message, you will not not run into the issue because "count = buffer.Length" and "offset = 0", so "count = buffer.Length - offset".

from websocketlistener.

Ah, I actually still have some code here:

WebSocketMessageReadStream message = await webSocket.ReadMessageAsync(mCancellationTokenSource.Token).ConfigureAwait(false);
byte[] buffer = new byte[4];
message.Read(buffer, 0, 4);

from websocketlistener.

Included in 2.1.8, Thanks again!

from websocketlistener.