01. ASP. Net Core 2.0 Web server and IIS decoupling, core

01. ASP. Net Core 2.0 Web server and IIS decoupling, core
01. ASP. Net Core 2.0 Web server and IIS decoupling I. historical problems before ASP. NET Core appeared, the Web servers of ASP. NET applications were all IIS. It is highly dependent on IIS and does not have scalability. Because IIS only has the Windows version and does not have a Linux version, ASP. NET Web applications can only run on Windows operating systems. 2. The OWIN specification appears as the OWIN (Open Web Interface fro. NET). This specification defines a set of interfaces used to decouple Web servers and Web applications. It standardizes and defines the mutual call relationship between Web servers and Web applications. That is to say, any Web server that implements the OWIN interface can support the running of ASP. NET Web applications. OWIN specification details can be accessed: http://owin.org/3, ASP. NET Core default Web server provided by the current implementation of the OWIN Interface WEB Server many, such as Katana, Kestrel and so on. The default WEB server provided by ASP. NET Core is Kestrel, which is cross-platform and can run on Linux or Windows operating systems. Iv. Web server usage posture under ASP. NET Core 2.0

• Classic Mode

Use Kestrel for SelfHost mode: Kestrel does not have security, cache, and other functions. Therefore, Kestrel should not be exposed to the public network.

• Reverse Proxy Mode

You can also use IIS and Nginx as reverse proxy servers: After the reverse proxy receives the Http Request, it is preprocessed and then forwarded to Kestrel for caching and security. Https://docs.microsoft.com/en-us/aspnet/core/fundamentals/servers/kestrel? Tabs = aspnetcore2x