IIS7.0 integration pipeline and module knowledge

Let's take a look at how IIS7.0 integrates request pipelines. Think of an integrated request pipeline as a set of basic linear steps, which must appear every time a page is provided (). In general, a certain authentication is required before authorization can be performed to retrieve the content, determine and execute the processing program required for the content, execute any necessary log records, and finally send a response.

The integrated request pipeline allows IIS7.0 to flexibly run different application frameworks at the same time. For example, you can run form authentication and custom logging modules on top of PHP content, all of which are implemented in the same pipeline.

IIS7.0 integrated pipelines and modules

Each website on the server has an integrated request pipeline and can run in either of two modes (integration mode or classic mode. The default integration mode allows you to insert specific function items into a pipeline, allowing you to precisely control the request process.

For compatibility consideration, the classic mode inserts the ISAPI module into the MPs queue to reproduce the IIS6.0/ISAPI function. This mode is useful when migrating applications to IIS7.0.