Incompatibility between ASP. NET 2 and IIS 7.0

We know that the main part of IIS 7.0 has been rewritten, and most of the rewriting involves the new integration mode, which allows. NET modules to be mounted at any stage of the IIS 7.0 pipeline. However, when ASP. NET is run in this integration mode, some incompatible changes will be revealed.

IIS 7.0 is a basic Internet service provided by Microsoft based on Microsoft Windows. It was originally an Optional package for the Windows NT version and was subsequently released together with Windows 2000, Windows XP Professional, and Windows Server 2003. However, IIS is not available in the commonly used Windows XP Home version.

The traditional HTTP Module and Handler must be reconfigured in the IIS 7.0web.config file;

Impersonation in the BeginRequest and AuthenticateRequest phases is no longer supported );

IIS 7.0 applications can no longer use both Form and Windows ID cards for verification;

Non-standard Http clients may encounter problems when using Windows Authentication because the authentication function has been moved to the kernel;

Other authentication problems caused at certain time points, such as when the client is performing identity simulation;

The global event Method DefaultAuthentication_OnAuthenticate is no longer supported, and the event WindowsAuthentication_OnAuthenticate is no longer triggered every time;

Passport verification has been permanently identified as expired. Unlike all previous incompatibility changes, this function will be permanently ineffective even if you run IIS 7.0 in traditional mode, passport is no longer valid.

We will explain the incompatibility between ASP. NET 2 and IIS 7.0.