You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Our software calls the PusherClient dll from unmanaged code (C++). As a result it uses TLS 1.0 as its security protocol.
For some unknown reason this is the default when a .net component is called from unmanaged code.
We resolved this by modifying WebSocket's constructor in Connection.cs to set it to SslProtocols.Tls12.
This is a quick fix that works for us.
Probably better to put this setting in the PusherOptions object?
The text was updated successfully, but these errors were encountered:
Our software calls the PusherClient dll from unmanaged code (C++). As a result it uses TLS 1.0 as its security protocol.
For some unknown reason this is the default when a .net component is called from unmanaged code.
We resolved this by modifying WebSocket's constructor in Connection.cs to set it to SslProtocols.Tls12.
This is a quick fix that works for us.
Probably better to put this setting in the PusherOptions object?
The text was updated successfully, but these errors were encountered: