Add protocol to "Now listening on" logged at startup
See original GitHub issueOn startup ASP.NET Core will log the addresses it is listening on. http
vs https
gives insight into whether the endpoint is secured with TLS. However there is no way to understand what protocols each endpoint supports. It would be useful when debugging connection errors to have an endpoint’s protocol logged.
For example:
Now listening on https://localhost:5000 (HTTP/1.1, HTTP/2)
Now listening on http://localhost:5001 (HTTP/2)
Issue Analytics
- State:
- Created 4 years ago
- Reactions:4
- Comments:8 (8 by maintainers)
Top Results From Across the Web
Removing Kestrel binding warning - asp.net core
When using Kestrel in an ASP.NET Core 2.1 project and specifying a binding in UseKestrel() , a message is logged at warning level:...
Read more >Configure endpoints for the ASP.NET Core Kestrel web ...
Learn about configuring endpoints with Kestrel, the cross-platform web server for ASP.NET Core.
Read more >Creating Launch Daemons and Agents
Explains how to write background processes that perform work on behalf of applications or serve content over the network.
Read more >WebSockets tutorial: How to go real-time with Node and ...
Implement the WebSocket protocol in Node.js and React, which offers a two-way communication mechanism between client and server.
Read more >Ultimate Running and debugging Node.js - IntelliJ IDEA
js run/debug configuration as described above and go to the Logs tab. Click the Add button next to the Log files to be...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
We’ll keep this around to talk about during Bedrock work (cc @davidfowl).
This isn’t possible with the current infrastructure. Hosting makes these logs and it only has access to IServerAddresses containing a simple list of urls.
To do this we’d have to redesign it so that the servers issued these logs. Even then it would only work on Kestrel. IIS and HttpSys don’t have access to this information at startup, only per request.