Kestrel will only bind to an IPEndPoint not an EndPoint

[Ninds]

Kestrel will only bind to an IPEndPoint not an EndPoint
Reproducer can be found here :
KestrelwithArbitraryEndPoint.cs
There is a runtime exception.

It appears it should have been fixed here Add support for listening to arbitrary endpoints.

OR .. perhaps I am doing something wrong.

The environment is .NET6

Kestrel with MemoryTransport
Consider adding an overload of Listen that takes an EndPoint

[davidfowl]

Here's the exception:

warn: Microsoft.AspNetCore.Server.Kestrel[0]
      Overriding address(es) 'https://localhost:7051, http://localhost:5051'. Binding to endpoints defined via IConfiguration and/or UseKestrel() instead.
Unhandled exception. System.InvalidOperationException: Operation is not valid due to the current state of the object.
   at Microsoft.AspNetCore.Server.Kestrel.Core.ListenOptions.GetDisplayName()
   at Microsoft.AspNetCore.Server.Kestrel.Core.ListenOptions.BindAsync(AddressBindContext context, CancellationToken cancellationToken)
   at Microsoft.AspNetCore.Server.Kestrel.Core.Internal.AddressBinder.EndpointsStrategy.BindAsync(AddressBindContext context, CancellationToken cancellationToken)
   at Microsoft.AspNetCore.Server.Kestrel.Core.Internal.AddressBinder.BindAsync(IEnumerable`1 listenOptions, AddressBindContext context, CancellationToken cancellationToken)
   at Microsoft.AspNetCore.Server.Kestrel.Core.KestrelServerImpl.BindAsync(CancellationToken cancellationToken)
   at Microsoft.AspNetCore.Server.Kestrel.Core.KestrelServerImpl.StartAsync[TContext](IHttpApplication`1 application, CancellationToken cancellationToken)
   at Microsoft.AspNetCore.Hosting.GenericWebHostService.StartAsync(CancellationToken cancellationToken)
   at Microsoft.Extensions.Hosting.Internal.Host.StartAsync(CancellationToken cancellationToken)
   at KestrelTransportDemo.Program.Main(String[] args) in C:\Users\david\source\repos\WebApplication9\WebApplication9\Program.cs:line 53
   at KestrelTransportDemo.Program.<Main>(String[] args)

It's coming from here

aspnetcore/src/Servers/Kestrel/Core/src/ListenOptions.cs

Line 127 in f9de7e4

throw new InvalidOperationException();

. Clearly these tests were inadequate 😞 because it doesn't work end to end.

Thanks for contacting us.

We're moving this issue to the .NET 7 Planning milestone for future evaluation / consideration. We would like to keep this around to collect more feedback, which can help us with prioritizing this work. We will re-evaluate this issue, during our next planning meeting(s).
If we later determine, that the issue has no community involvement, or it's very rare and low-impact issue, we will close it - so that the team can focus on more important and high impact issues.
To learn more about what to expect next and how this issue will be handled you can read more about our triage process here.

[halter73]

I opened #40003 to fix this. Hopefully we can get it backported to .NET 6 too. It looks like this has been a problem since .NET 5.

Another possible workaround other than doing public class MemoryEndPoint_WithWorkaround : IPEndPoint is to have the MemoryConnectionListener.EndPoint return a IPEndPoint , UnixDomainSocketEndPoint or FileHandleEndPoint. The IConnectionListener.EndPoint property is only used to populate the IServerAddressesFeature which is generally only used to display the listening address.

Edit: I decided against trying the backport given the evidently limited usage and possible workaround.