Web applications in IIS 7.0 come in two configuration forms: classic and integrated.
The classic form is to be compatible with the previous version, using the ISAPI extension to call the ASP.NET running library, and the web application originally running under IIS6.0 only needs to be configured in the classic form to IIS7.0, and the code can run normally without any modifications.
The integration form is a unified begging pipeline that combines the ASP.NET plea pipeline with the IIS central pipeline, which provides better performance, modularity in configuration and management, and increased agility when extending IIS with managed code modules. Assuming that the old web application is running in the integrated form of IIS 7.0, it may need to stop modifying the application's web.config file, especially if it uses a custom module that completes the IHttpHandler interface. IIS 7.0 can support both forms of application on the same server.
web.config file
The system.webServer section specifies the IIS7.0 settings applied to the web application, whose parent node is configuration, and what can be set in this node includes:
The defaultDocument returned by the web servant to the client when the pleading does not contain the specified resource; httpCompression Custom Headers (httpProtocol Section) modules Handlers
Some of these settings apply only to the integrated form, but not to the classic form, such as applications running in the classic form neglect all managed code modules and disposals specified in the system.WebServer section of web.config, where the web application should define modules and disposals in httpModules and httpHandlers in the syste.web section. |
Posted on 3/14/2018 12:30:54 PM
|
|
|
Posted on 7/11/2018 1:59:57 PM
|
Landlord|
Posted on 7/11/2018 2:07:42 PM
|
