Skip to content
New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

#

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

Jump to bottom

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

Open
antonfirsov opened this issue Jan 25, 2021 · 3 comments
Open

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

antonfirsov opened this issue Jan 25, 2021 · 3 comments
Labels
area-System.Net.Sockets
Milestone
Future

Comments

@antonfirsov
Copy link
Member

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.
@dotnet-issue-labeler dotnet-issue-labeler bot added area-System.Net.Sockets untriaged New issue has not been triaged by the area owner labels Jan 25, 2021
@ghost
Copy link

ghost commented Jan 25, 2021

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
Copy link
Contributor

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

@antonfirsov antonfirsov mentioned this issue Jan 26, 2021
Merged
@antonfirsov 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
@ManickaP
Copy link
Member

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

@ManickaP ManickaP removed the untriaged New issue has not been triaged by the area owner label Feb 18, 2021
@ManickaP ManickaP added this to the Future milestone Feb 18, 2021
# for free to join this conversation on GitHub. Already have an account? # to comment
Assignees
No one assigned
Labels
area-System.Net.Sockets
Projects
None yet
Milestone
Future
Development

No branches or pull requests
3 participants
@antonfirsov @ManickaP @MichalPetryka