Step-by-Step parsing of ASP. NET Request Response flowchart (B/S IIS)

To remember deeply: I will repeat it in words.

1. the browser encapsulates the request information into an HTTP packet and sends it to the server.

2. IIS is responsible for listening to port 80 and receiving browser packets.Static files, Find the static file from the server and convert it to byte [], and then send the response to the browser through the proxy socket.

3. If dynamic files cannot be processed by IIS and cannot be transferred to the aspnet_isapi.dll extension, the extension will send the request to the. netframework CLR for processing (that is, the Asp.net lifecycle ).

Step 2

Iis's core process inetinfo.exe is handed over to aspnet_isapi.dll

The extended startup clr(workprocessprocess is that the appdomain of aspnet_wp.exe(xpiis5), w3wp.exe (IIS6, iis7) is handed over to isapiruntime for general processing.ProgramAfter the processrequest method is processed, return the final response to aspnet_isapi.dll to the browser.

Step 3

Isapiruntime. processrequest uses the ECB handle to create an httpworkrequest (which encapsulates the packet header). Call httpruntim. Pr () to create an httpcontext Based on the ECB handle.

Get httpapplication from httpapplicationfactory and take 23 pipeline events