Connection closed when sending more than 126 bytes in a given message via WebSocket

[KieranDevvs]

When sending a message of 126 bytes or more to System.Net.WebSockets.ClientWebSocket, the connection forcibly closes. Any messages with 125 bytes or less are received as expected.

I have tested System.Net.WebSockets.ClientWebSocket under a Blazor WASM client environment (using the browser API) and also from a console app, both tests fail. However, other websocket client implementations such as WebSocket4Net work with Bedrock being the server. I have also tested System.Net.WebSockets.ClientWebSocket with another WebSocket server and it appears to work as intended which indicates there is some compatibility issues with Bedrock WebSockets.

Unhandled exception rendering component: The WebSocket is in an invalid state ('Closed') for this operation. Valid states are: 'Open, CloseSent'
System.Net.WebSockets.WebSocketException (0x80004005): The WebSocket is in an invalid state ('Closed') for this operation. Valid states are: 'Open, CloseSent'
   at System.Net.WebSockets.BrowserWebSocket.ReceiveAsync(ArraySegment`1 buffer, CancellationToken cancellationToken)
   at ClientConnection.ListenAsync(CancellationToken cancellationToken) in BedrockWebSocketTest.Client\ClientConnection.cs:line 28
   at BedrockWebSocketTest.Client.Pages.Index.Start() in BedrockWebSocketTest.Client\Pages\Index.razor:line 16
   at Microsoft.AspNetCore.Components.ComponentBase.CallStateHasChangedOnAsyncCompletion(Task task)
   at Microsoft.AspNetCore.Components.RenderTree.Renderer.GetErrorHandledTask(Task taskToHandle, ComponentState owningComponentState)

Here is a project solution to reproduce the issue: https://github.com/KieranDevvs/BedrockWebSocketTest

Run both projects, and hit start within the index page of the Blazor WASM web app. You should see the connection drop. Now go into SessionHandler.cs within the server project and change Enumerable.Range(0, 15).Select(x => "really") to Enumerable.Range(0, 14).Select(x => "really") to lower the message size from 128 to 121. When you run the test this time, the message is received within the client and is printed to the console.

[KieranDevvs]

Had some time tonight to dig a little deeper, it appears the client is failing when its attempting to validate the header payload is UFT8.

[KieranDevvs]

Tested the same client out with the following server with success:

public class ConsoleServer
    {
        static HttpListener httpListener = new HttpListener();
        private static Mutex signal = new Mutex();
        public static async Task Main(string[] args)
        {
            httpListener.Prefixes.Add("http://localhost:1337/");
            httpListener.Start();
            Console.WriteLine("Accepting connections");
            while (signal.WaitOne())
            {
                ReceiveConnection();
            }

        }

        public static async Task ReceiveConnection()
        {
            HttpListenerContext context = await
            httpListener.GetContextAsync();
            if (context.Request.IsWebSocketRequest)
            {
                HttpListenerWebSocketContext webSocketContext = await context.AcceptWebSocketAsync(null);
                WebSocket webSocket = webSocketContext.WebSocket;
                if (webSocket.State == WebSocketState.Open)
                {
                    var payload = Encoding.UTF8.GetBytes($"This is a {string.Join(" ", Enumerable.Range(0, 20).Select(x => "really"))} long message.");
                    await webSocket.SendAsync(payload, WebSocketMessageType.Binary, true, CancellationToken.None);
                }
            }
            signal.ReleaseMutex();
        }
    }

[davidfowl]

Thanks for the repro