我遇到了这个问题，受到@Jeremy Cook的回答的启发，我咬紧牙关，想知道到底是什么原因导致iis7集成模式不像我的web.config。以下是我的设想:

Web API(版本4.0.030506.0即旧版本) net 4.0 属性路由3.5.6为Web API[剧透警告:它是这个家伙!］

我想在一个必须使用. net 4的项目中使用属性路由(不幸的是)，因此不能使用Web API 2.2(需要. net 4.5)。NuGet包善意地将此部分添加到<system。web >部分:

<system.web>
<httpHandlers>
      <add verb="*" path="routes.axd" type="AttributeRouting.Web.Logging.LogRoutesHandler, AttributeRouting.Web" />
    </httpHandlers>
</system.web>

[我说的是善意的，因为旧版本的IIS需要这部分]

删除这个部分让我通过了HTTP 500.23!!

简介: 我赞同杰里米的话，理解事情为什么不起作用而不仅仅是“掩盖症状”是很重要的。即使你必须掩盖症状，你也知道你在做什么(以及为什么):-)

我们在部署Azure应用程序服务时遇到了这个问题。我们的问题是我们必须从系统中移动模块。Web /httpmodules到system.webserver/modules。按工作方式移动子条目。这似乎与应用程序的年龄和它在升级到Azure应用程序服务之前运行的IIS实例有关。

检查配置文件中是否存在这些键

<configuration>
    <system.webServer>
        <validation validateIntegratedModeConfiguration="false"/>
    </system.webServer>
</configuration>

添加<validation validateIntegratedModeConfiguration="false"/>可以解决问题，但并不适用于所有情况。我已经在这个问题上跑了几次，我希望帮助其他人不仅克服这个问题，而且理解它。(随着iis6逐渐成为神话和谣言，这一点变得越来越重要。)

背景:

这个问题和围绕它的困惑始于ASP的引入。NET 2.0和iis7。IIS 6过去和现在都只有一种管道模式，它相当于IIS 7+所称的“经典”模式。对于运行在iis7 +上的所有应用程序，第二种较新的、推荐的管道模式称为“集成”模式。

那么，有什么不同呢?关键的区别在于ASP。NET与IIS交互。

Classic mode is limited to an ASP.NET pipeline that cannot interact with the IIS pipeline. Essentially a request comes in and if IIS 6/Classic has been told, through server configuration, that ASP.NET can handle it then IIS hands off the request to ASP.NET and moves on. The significance of this can be gleaned from an example. If I were to authorize access to static image files, I would not be able to do it with an ASP.NET module because the IIS 6 pipeline will handle those requests itself and ASP.NET will never see those requests because they were never handed off.* On the other hand, authorizing which users can access a .ASPX page such as a request for Foo.aspx is trivial even in IIS 6/Classic because IIS always hands those requests off to the ASP.NET pipeline. In Classic mode ASP.NET does not know what it hasn't been told and there is a lot that IIS 6/Classic may not be telling it. Integrated mode is recommended because ASP.NET handlers and modules can interact directly with the IIS pipeline. No longer does the IIS pipeline simply hand off the request to the ASP.NET pipeline, now it allows ASP.NET code to hook directly into the IIS pipeline and all the requests that hit it. This means that an ASP.NET module can not only observe requests to static image files, but can intercept those requests and take action by denying access, logging the request, etc.

克服错误:

If you are running an older application that was originally built for IIS 6, perhaps you moved it to a new server, there may be absolutely nothing wrong with running the application pool of that application in Classic mode. Go ahead you don't have to feel bad. Then again maybe you are giving your application a face-lift or it was chugging along just fine until you installed a 3rd party library via NuGet, manually, or by some other means. In that case it is entirely possible httpHandlers or httpModules have been added to system.web. The outcome is the error that you are seeing because validateIntegratedModeConfiguration defaults true. Now you have two choices: Remove the httpHandlers and httpModules elements from system.web. There are a couple possible outcomes from this: Everything works fine, a common outcome; Your application continues to complain, there may be a web.config in a parent folder you are inheriting from, consider cleaning up that web.config too; You grow tired of removing the httpHandlers and httpModules that NuGet packages keep adding to system.web, hey do what you need to. If those options do not work or are more trouble than it is worth then I'm not going to tell you that you can't set validateIntegratedModeConfiguration to false, but at least you know what you're doing and why it matters.

好读:

ASP。IIS 7.0上的NET 2.0突破性更改 ASP。与iis7集成 HTTP处理程序和HTTP模块概述

当然，有很多方法可以把各种奇怪的东西放到ASP中。NET管道从iis6 /Classic通过咒语，如通配符映射，如果你喜欢这样的事情。

以下步骤解决了我的问题:

使用管理员权限打开CMD提示符。

执行命令iisreset。

希望这能有所帮助。

我遇到了这个问题，受到@Jeremy Cook的回答的启发，我咬紧牙关，想知道到底是什么原因导致iis7集成模式不像我的web.config。以下是我的设想:

Web API(版本4.0.030506.0即旧版本) net 4.0 属性路由3.5.6为Web API[剧透警告:它是这个家伙!］

我想在一个必须使用. net 4的项目中使用属性路由(不幸的是)，因此不能使用Web API 2.2(需要. net 4.5)。NuGet包善意地将此部分添加到<system。web >部分:

<system.web>
<httpHandlers>
      <add verb="*" path="routes.axd" type="AttributeRouting.Web.Logging.LogRoutesHandler, AttributeRouting.Web" />
    </httpHandlers>
</system.web>

[我说的是善意的，因为旧版本的IIS需要这部分]

删除这个部分让我通过了HTTP 500.23!!

简介: 我赞同杰里米的话，理解事情为什么不起作用而不仅仅是“掩盖症状”是很重要的。即使你必须掩盖症状，你也知道你在做什么(以及为什么):-)