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
Has anyone else experienced the above issue with Wonde client?
{
"Message": "An error has occurred.",
"ExceptionMessage": "An existing connection was forcibly closed by the remote host",
"ExceptionType": "System.Net.Sockets.SocketException",
"StackTrace": " at System.Net.Sockets.NetworkStream.Read(Byte[] buffer, Int32 offset, Int32 size)"
}
From recent experience with MS Graph Api and Microsoft depricating TLS 1.0 and TLS 1.1 security protocols (as of mid February) I had to deal with this exact issue where HttpClient kept dropping connection on some endpoints.
Upgrading my project to .Net 4.6.1 partly fixed the issue. But to completely get around the issue I had to explicitly set security protocols while HttpClient was instantiated as below.
Has anyone else experienced the above issue with Wonde client?
From recent experience with MS Graph Api and Microsoft depricating TLS 1.0 and TLS 1.1 security protocols (as of mid February) I had to deal with this exact issue where
HttpClient
kept dropping connection on some endpoints.Upgrading my project to
.Net 4.6.1
partly fixed the issue. But to completely get around the issue I had to explicitly set security protocols whileHttpClient
was instantiated as below.Is there any way to do something similar with
Wonde.Client()
?The text was updated successfully, but these errors were encountered: