sta / sta/websocket-sharp

WebSocket Server is causing the error message below every 5 seconds

Open
#736 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
C#
Stars
6.1k
Forks
1.7k
PR merge metrics
No merged PRs in 30d

Description

[9/9/2023 4:37:00 AM] DEBUG <>c__DisplayClass66_0.b__0:791

System.IO.IOException: Authentication failed because the remote party has closed the transport stream.
at System.Net.Security.SslState.StartReadFrame(Byte[] buffer, Int32 readBytes, AsyncProtocolRequest asyncRequest)
at System.Net.Security.SslState.StartReceiveBlob(Byte[] buffer, AsyncProtocolRequest asyncRequest)
at System.Net.Security.SslState.ForceAuthentication(Boolean receiveFirst, Byte[] buffer, AsyncProtocolRequest asyncRequest, Boolean renegotiation)
at System.Net.Security.SslState.ProcessAuthentication(LazyAsyncResult lazyResult)
at WebSocketSharp.Net.WebSockets.TcpListenerWebSocketContext..ctor(TcpClient tcpClient, String protocol, Boolean secure, ServerSslConfiguration sslConfig, Logger log) in D:\WebSocketSharp\websocket-sharp\websocket-sharp\Net\WebSockets\TcpListenerWebSocketContext.cs:line 93
at WebSocketSharp.Server.WebSocketServer.<>c__DisplayClass66_0.b__0(Object state) in D:\WebSocketSharp\websocket-sharp\websocket-sharp\Server\WebSocketServer.cs:line 791

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with Net/WebSockets/TcpListenerWebSocketContext.cs at line 93 and Server/WebSocketServer.cs at line 791, using the reported SslState stack trace as the entry point. Reproduce the repeated authentication failure if possible and inspect the surrounding connection-handling flow. Done means identifying why the remote party closes the transport stream and verifying the resulting behavior.

Written by the indexing model from the issue text.

Assessment

Tech stack
csharp
Domain
networking
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.