Socket.Shutdown() for UDP sockets: valid on Windows but leads to SocketException on Unix

[antonfirsov]

Follow up on #47229 (comment) from #47229.

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.

Tagging subscribers to this area: @dotnet/ncl
See info in area-owners.md if you want to be subscribed.

Issue Details

---

Follow up on #47229 (comment) from #47229.

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.

Author:	antonfirsov
Assignees:	-
Labels:	area-System.Net.Sockets, untriaged
Milestone:	-

[MichalPetryka]

The issue title should probably be Socket.Shutdown() for UDP sockets: valid on Windows but leads to SocketException on Unix

[ManickaP]

Triage: discovered during our tests, not reported by a customer, pushing to future.