Exception

4/22/2022 11:53:27 PM|Fatal|QueueUserWorkItemCallback.WaitCallback_Context|WebSocketSharp.WebSocketException: An exception has occurred while reading an HTTP request/response. ---> System.IO.IOException: Unable to read data from the transport connection: An existing connection was forcibly closed by the remote host. ---> System.Net.Sockets.SocketException: An existing connection was forcibly closed by the remote host
                               at System.Net.Sockets.Socket.Receive(Byte[] buffer, Int32 offset, Int32 size, SocketFlags socketFlags)
                               at System.Net.Sockets.NetworkStream.Read(Byte[] buffer, Int32 offset, Int32 size)
                               --- End of inner exception stack trace ---
                               at System.Net.Sockets.NetworkStream.Read(Byte[] buffer, Int32 offset, Int32 size)
                               at System.IO.Stream.ReadByte()
                               at WebSocketSharp.HttpBase.readHeaders(Stream stream, Int32 maxLength)
                               at WebSocketSharp.HttpBase.Read[T](Stream stream, Func`2 parser, Int32 millisecondsTimeout)
                               --- End of inner exception stack trace ---
                               at WebSocketSharp.HttpBase.Read[T](Stream stream, Func`2 parser, Int32 millisecondsTimeout)
                               at WebSocketSharp.HttpRequest.Read(Stream stream, Int32 millisecondsTimeout)
                               at WebSocketSharp.Net.WebSockets.TcpListenerWebSocketContext..ctor(TcpClient tcpClient, String protocol, Boolean secure, ServerSslConfiguration sslConfig, Logger logger)
                               at WebSocketSharp.Ext.GetWebSocketContext(TcpClient tcpClient, String protocol, Boolean secure, ServerSslConfiguration sslConfig, Logger logger)
                               at WebSocketSharp.Server.WebSocketServer.<>c__DisplayClass1.<receiveRequest>b__0(Object state)

And this is my client

the server

sry for writing this awful shit

Update: I tried using nginx as a reverse proxy and now it looks like this

4/23/2022 8:16:44 AM|Fatal|QueueUserWorkItemCallback.WaitCallback_Context|WebSocketSharp.WebSocketException: An exception has occurred while reading an HTTP request/response. ---> System.IO.EndOfStreamException: The header cannot be read from the data source.
                              at WebSocketSharp.HttpBase.<>c__DisplayClass1.<readHeaders>b__0(Int32 i)
                              at WebSocketSharp.Ext.EqualsWith(Int32 value, Char c, Action`1 action)
                              at WebSocketSharp.HttpBase.readHeaders(Stream stream, Int32 maxLength)
                              at WebSocketSharp.HttpBase.Read[T](Stream stream, Func`2 parser, Int32 millisecondsTimeout)
                              --- End of inner exception stack trace ---
                              at WebSocketSharp.HttpBase.Read[T](Stream stream, Func`2 parser, Int32 millisecondsTimeout)
                              at WebSocketSharp.HttpRequest.Read(Stream stream, Int32 millisecondsTimeout)
                              at WebSocketSharp.Net.WebSockets.TcpListenerWebSocketContext..ctor(TcpClient tcpClient, String protocol, Boolean secure, ServerSslConfiguration sslConfig, Logger logger)
                              at WebSocketSharp.Ext.GetWebSocketContext(TcpClient tcpClient, String protocol, Boolean secure, ServerSslConfiguration sslConfig, Logger logger)
                              at WebSocketSharp.Server.WebSocketServer.<>c__DisplayClass1.<receiveRequest>b__0(Object state)

Start by reproducing the client/server connection using the direct setup and the nginx reverse-proxy setup described in the issue. Trace the failures through WebSocketServer.receiveRequest, TcpListenerWebSocketContext, HttpRequest.Read, and HttpBase.readHeaders, comparing the two stack traces. Done means the connection-close behavior has a confirmed cause and the appropriate handling is covered by a demonstrated fix or test.