Websocket state: Closed
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 6.1k
- Forks
- 1.7k
- PR merge metrics
- No merged PRs in 30d
Description
I am trying to connect to a local application with tls 1.3.
This is my code:
using (var ws = new WebSocket("wss://localhost:55400/"))
{
ws.OnMessage += (sender, e) =>
OnMessage(sender, e);
ws.SslConfiguration.ClientCertificates = Authentification.CertificateCollection;
ws.SslConfiguration.EnabledSslProtocols = System.Security.Authentication.SslProtocols.Tls13;
ws.Connect();
WebSocketState state = ws.ReadyState;
ws.Send(context);
//Console.ReadKey(true);
}
Wireshark states that some connection attempt is mate bu no cleint hello / handshake
plattform is windows 10 21H2
error message: An Exception has ocurred while connecting (code 1015)
log: none
connection: closed
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No repository files or tests are named. Start by reproducing the supplied WebSocket client and TLS 1.3 configuration on Windows 10, then inspect the connection and TLS-handshake path to determine why no client hello is sent and the connection closes with code 1015. Done means the cause is identified and covered by a reproducible validation.
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