System.Net.HttpListener.GetContext() throws HttpListenerException with ErrorCode=HttpStatusCode.InternalServerError on Linux after Stop()

[inikulshin]

Description

When System.Net.HttpListener.GetContext() is called after System.Net.HttpListener.Stop() on Linux, HttpListenerException with ErrorCode=HttpStatusCode.InternalServerError is thrown.

On Windows it's ErrorCode=SocketError.OperationAborted, and imo they should be aligned for all OSes.

Here is non-Windows code that throws:

runtime/src/libraries/System.Net.HttpListener/src/System/Net/Managed/ListenerAsyncResult.Managed.cs

Lines 69 to 70 in 05ed884

	if (_inGet && (exc is ObjectDisposedException))
	_exception = new HttpListenerException((int)HttpStatusCode.InternalServerError, SR.net_listener_close);

Reproduction Steps

.

Expected behavior

Same HttpListenerException.ExitCode on all OSes or System.InvalidOperationException, as API declares:

https://learn.microsoft.com/en-us/dotnet/api/system.net.httplistener.getcontext?view=net-10.0#exceptions

InvalidOperationException
This object has not been started or is currently stopped.

Actual behavior

When System.Net.HttpListener.GetContext() is called after System.Net.HttpListener.Stop() on Linux, HttpListenerException with ErrorCode=HttpStatusCode.InternalServerError is thrown.

On Windows it's ErrorCode=SocketError.OperationAborted.

Regression?

No response

Known Workarounds

No response

Configuration

No response

Other information

No response

[dotnet-policy-service]

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

[wfurt]

seems like good cleanup.