Expose Socket via a Kestrel ConnectionContext feature

[halter73]

Is your feature request related to a problem? Please describe.

We should make it so you don't have to resort to something like the following to access the managed Socket if you really want to.

var socket = (Socket)connectionContext.GetType().GetField("_socket", BindingFlags.NonPublic | BindingFlags.Instance).GetValue(connectionContext);

Proposed API

using System.Net.Sockets;

namespace Microsoft.AspNetCore.Connections.Features
{
+    public interface IConnectionSocketFeature
+   {
+        Socket? Socket { get; }
+    }
}

Usage Examples

var socket = connectionContext.Features.Get<IConnectionSocketFeature>().Socket;

Thanks for contacting us.
We're moving this issue to the Next sprint planning milestone for future evaluation / consideration. We will evaluate the request when we are planning the work for the next milestone. To learn more about what to expect next and how this issue will be handled you can read more about our triage process here.

[BrennanConroy]

What are examples of usage for this? What settings do you want after creation of the socket?

[BrennanConroy]

What are examples of usage for this?

Force a reset.

[davidfowl]

Another use case that came up last week was the ability to get tcp information via a new ioctl SIO_TCP_INFO https://docs.microsoft.com/en-us/windows/win32/winsock/sio-tcp-info.