Kerry Jiang

It is on the way: https://github.com/kerryjiang/SuperSocket/tree/master/src/SuperSocket.WebSocket WebSocket4Net should be base on SuperSocket.WebSocket. That means server side and client side share the same protocol implementation.

Actually there is already a .net core version in NuGet: https://www.nuget.org/packages/WebSocket4Net/0.15.2 Which targets .netstandard 1.3 which is compatible with .NET Core 2.2 and .net standard 2.0. The one I mentioned...

I don't think so. The project targets high standard can reference the libraries which target to lower .netstandard. > .NET implementation support The following table lists the minimum platform versions...

Just only keep the first parameter in the constructor. The other two are not necessary. Make sure the certificate of your server side is setup correct.

The second parameter is not for transfer level security protocol like SSL/TLS. Instead, it's for application level sub protocol. There is a constructor with only one required parameter, other parameters...

@DragonFly81 Hello, there is already a constructor allowing the SslProtocols parameter in the latest WebSocket4Net.

@jmortlock Could you try the latest beta version? https://www.nuget.org/packages/WebSocket4Net/0.15.0-beta2 You can setup SslProtocols through the new property "Securiity".

Yes, but the properties of Security are not.

Can it be reproduced outside docker?

Ok, I'll check this issue soon. That would be great, if you provide some test cases.