AppHost log prints HTTP2 endpoint that I can't click

[eerhardt]

When I dotnet run an Aspire app, it prints 2 URLs it is listening to. One that works, and one I shouldn't click:

If I click that 2nd URL, it gives me

We shouldn't be showing that URL as it is confusing which URL to click.

[DamianEdwards]

This is logged by ASP.NET itself as it logs all configured endpoints, including those only listening on http/2. I don't think we can suppress this being logged from the Dashboard level (this is the OTLP endpoint the Dashboard hosts).

[davidfowl]

We can. We do the same with the other logs in a really hacky interesting way

[davidfowl]

We should attempt to fix this for preview1 @mitchdenny? Suppress the dashboard logs and write our own.

[mitchdenny]

We should still output a URL, but our own custom message. I'll have a go at suppressing it.

[JamesNK]

If I click that 2nd URL, it gives me

We shouldn't be showing that URL as it is confusing which URL to click.

Let's all take a moment to appreciate how clear and understandable this error message is—sent from an HTTP/2-only endpoint over an HTTP/1.1 connection. Thank you Kestrel 🙏

[davidfowl]

Look at this https://github.com/dotnet/sdk/blob/91271e341e77f3c3c24bbf7b945fefaf98cff72c/src/BuiltInTools/dotnet-watch/Filters/LaunchBrowserFilter.cs#L13

It turns out dotnet watch looks at the output to figure out what url to launch 👀