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
This is a behavioral difference between the OS-es, on Unix a call to shutdown(sockfd, how) returns ENOTCONN for UDP sockets. We may or may not want to address it in our code for compatibility.
The text was updated successfully, but these errors were encountered:
This is a behavioral difference between the OS-es, on Unix a call to shutdown(sockfd, how) returns ENOTCONN for UDP sockets. We may or may not want to address it in our code for compatibility.
antonfirsov
changed the title
Socket.Shutdown() for UDP sockets: valid on Windows but leads to SocketException on windows
Socket.Shutdown() for UDP sockets: valid on Windows but leads to SocketException on Unix
Jan 27, 2021
Follow up on #47229 (comment) from #47229.
This is a behavioral difference between the OS-es, on Unix a call to
shutdown(sockfd, how)
returnsENOTCONN
for UDP sockets. We may or may not want to address it in our code for compatibility.The text was updated successfully, but these errors were encountered: