IIS Request Processing

As you have read my earlier topic "Introduction to IIS Architectures".
You can find it here http://shareinkt.blogspot.com/2015/08/introduction-to-iis-architectures.html
 
This topic describes how a client request is processed on an IIS server.

Request Processing by Type of Request

The following table describes what happens once an IIS process receives a request to be executed.
RequestAction
HTML PageIIS returns the page in HTML format.
A file whose extension is mapped to a particular ISAPI extension, such as Asp.dllIIS loads the appropriate DLL file and presents the request through the Extension_Control_Block data structure. For example, the .asp extension is mapped to Asp.dll, so that all requests for files with an .asp extension will be directed to Asp.dll. The .stm and .shtm extensions are mapped to the Ssinc.dll.
ISAPI extensionIIS loads the ISAPI DLL (if it is not already running) and the request is sent to the extension through the EXTENSION_CONTROL_BLOCK Structure data structure.
CGI applicationIIS creates a new process. IIS will then provide the query string and other parameters that are included with the request through the environment and standard input (STDIN) handle for the process.
ISAPI filters are always loaded as long as the Web service is running and a request to the server has been made.

Preliminary Request Processing on IIS 6.0 in Workder Process Isolation Mode

Before an IIS process receives a request to execute, some preliminary processing occurs that is described in the following steps:

  1. A request arrives at HTTP.sys.
  2. HTTP.sys determines if the request is valid. If the request is not valid, it sends a code for an invalid request back to the client.
  3. If the request is valid, HTTP.sys checks to see if the request is for static content (HTML) because static content can be served immediately.
  4. If the request is for dynamic content, HTTP.sys checks to see if the response is located in its kernel-mode cache.
  5. If the response is in the cache, HTTP.sys returns the response immediately.
  6. If the response is not cached, HTTP.sys determines the correct request queue, and places the request in that queue.
  7. If the queue has no worker processes assigned to it, HTTP.sys signals the WWW service to start one.
  8. The worker process pulls the request from the queue and processes the request, evaluating the URL to determine the type of request (ASP, ISAPI, or CGI).
  9. The worker process sends the response back to HTTP.sys.
  10. HTTP.sys sends the response back to the client and logs the request, if configured to do so.

Preliminary Request Processing on IIS 6.0 in IIS 5.0 Isolation Mode and Earlier Versions of IIS

The request processing of IIS 6.0 running in IIS 5.0 isolation mode is nearly identical to the request processing in IIS 5.1, IIS 5.0, and IIS 4.0. Before an IIS process receives a request to execute, some preliminary processing occurs that is described in the following steps:

  1. A request arrives. If the requested application is running in-process, then Inetinfo.exe takes the request. If not, then DLLHost.exe takes the request.
  2. Inetinfo.exe or DLLHost.exe determines if the request is valid. If the request is not valid, it sends a code for an invalid request back to the client.
  3. If the request is valid, Inetinfo.exe or DLLHost.exe checks to see if the response is located in the IIS cache.
  4. If the response is in the cache, it is returned immediately.
  5. If the response is not cached, Inetinfo.exe or DLLHost.exe processes the request, evaluating the URL to determine if the request is for static content (HTML), or dynamic content (ASP, ASP.NET or ISAPI).
  6. The response is sent back to the client and the request is logged, if IIS is configured to do so.

Comments

Post a Comment

Popular posts from this blog

Export Data as csv file from SQL server using command line tools

In the post we will be discussing about the ways of exporting data from SQL server to csv file. As per the use case the output should have: Header row The seperator of columns should be ",". The file should be encoded as UTF-8. There are two tools for exporting data from SQL Server to csv file. These are sqlcmd and bcp. SQLCMD The command which can be used for this purpose is Sqlcmd -S "<ServerName\InstanceName>" -d "<DatabaseName>" -U "<UserName>" -P "<Password>" -i "<SQLScriptFilePath>" -W -f 65001 -h -1 -s "," -o "<OutputFilePath>" E.g.:  Sqlcmd -S "10.00.00.00" -d "EmployeeDatabase" -U "User1" -P "Password" -i "Script1.sql" -W -f 65001 -h -1 -s "," -o "c:\File.csv" Attributes -W is used to remove all the whitespaces -h -1 is used to remove the header (if header is not remo...
Read more

Query within a Task Scheduler Library folder using schtasks.exe and getting total number of tasks

As we all know that working with task scheduler is not an easy task when it comes to query, change, add etc. through the command prompt. Here i will share few of the details while working with schtasks.exe. What is Schtasks.exe ? Schtasks enables an administrator to create, delete, query, change, run, and end scheduled tasks on a local or remote computer. Running Schtasks.exe without arguments displays the status and next run time for each registered task. For more information to work with Schtasks follow the link " https://docs.microsoft.com/en-us/windows/desktop/taskschd/schtasks " Now lets get back to what our topic concerns -  Query within a Task Scheduler Library folder using schtasks.exe and getting total number of tasks. For Query we just use  - schtasks.exe /query /TN \[FolderName]\ Now to query and get the number of tasks we will follow below process : Just for an example I'm working for two folder - \Microsoft\Windows\SideShow and \Micros...
Read more

Getting Started with AppCmd.exe

Overview AppCmd.exe is the single command line tool for managing IIS 7 and above. It exposes all key server management functionality through a set of intuitive management objects that can be manipulated from the command line or from scripts. AppCmd enables you to easily control the server without using a graphical administration tool and to quickly automate server management tasks without writing code. Some of the things you can do with AppCmd: Create and configure sites, apps, application pools, and virtual directories Start and stop sites, and recycle application pools List running worker processes, and examine currently executing requests Search, manipulate, export, and import IIS and ASP.NET configuration AppCmd also allows server administrators to build advanced management tasks simply by combining multiple simpler AppCmd.exe commands, or reusing the output of the tool inside another program. This article contains: How to Use AppCmd.exe Getting H...
Read more