IIS managed pipeline mode integration and classic

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 ProcessingProgramIt is not 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> \

 

 

Conclusion: I am very sorry that the errors caused by the two systems are not related to the program, but to the server deployment, it is also the responsibility of programmers and system administrators. First of all, programmers do not know how to deploy Windows Server 2008. The options for deploying different systems and programs vary with the program syntax. We cannot blame the system administrator, because the system administrator is not clear about the system program, we cannot pray that the system administrator can help us successfully deploy the program. Therefore, as a programmer, we must be very clear about system deployment.