Server implementations in ASP.NET Core
ReviewCoreASPHostingg.NET | Best and cheap ASP.NET Core 1.0 Hosting. An ASP.NET Core application runs with an in-process HTTP server implementation. The server implementation listens for HTTP requests and surfaces them to the application as sets of request features composed into an HttpContext.
ASP.NET Core ships two server implementations:Kestrel is a cross-platform HTTP server based on libuv, a cross-platform asynchronous I/O library.
WebListener is a Windows-only HTTP server based on the Http.Sys kernel driver.Kestrel
Kestrel is the web server that is included by default in ASP.NET Core new-project templates. If your application accepts requests only from an internal network, you can use Kestrel by itself.If you expose your application to the Internet, we recommend that you use IIS, Nginx, or Apache as a reverse proxy server. A reverse proxy server receives HTTP requests from the Internet and forwards them to Kestrel after some preliminary handling, as shown in the following diagram.The most important reason for using a reverse proxy for edge deployments...