The classic difference between the integration and the Classic Mode of the managed pipeline deployed in IIS is that the iis Pipeline
Summary of ESPS and SCSJ in Windows server 2008
The problem with SCSJ lies in the choice of the integration mode and the classic mode, and the system itself is normal. When deploying the system, we chose the integration mode, which made the HttpHandlers node of WebConfig inaccessible.
In integration mode, the HTTP module and HTTP handler are no longer defined in <system. web>, but in <system. webServer>. If you run a web. config file that includes the HTTP module or HTTP processing program in integration mode, it will become invalid.
In integration mode, you must add a <system. the webServer> \
The specific conversion method is as follows:
In Classic mode,The HTTP handler registration method isAdd a <system. web >\< httpHandler> node:
In integration mode,The HTTP handler registration method isAdd a <system. webServer >\< handlers> node:
The applicant's name cannot be included in the integration mode unless it is changed to the classic mode.
In integration mode, the applicant can bring it out because the <system. webServer> \