blocks|key|359168|text|I您使用的是Visual+Studio+2012，请下载并安装Microsoft最近发布的更新2(截至2013年4月)。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|359169|Visual+Studio+2012+Update+2|offset|length|359170|该更新中有一些与该问题相关的错误修复。|359171|entityMap|0|LINK|mutability|MUTABLE|url|http://support.microsoft.com/kb/2797912^0|0|0|R|0|0|0^^$0|@$1|2|3|4|5|6|7|P|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|Q|8|@]|9|@$D|R|E|S|1|T]]|A|$]]|$1|F|3|G|5|6|7|U|8|@]|9|@]|A|$]]|$1|H|3|-4|5|6|7|V|8|@]|9|@]|A|$]]]|I|$J|$5|K|L|M|A|$N|O]]]]

I you are using Visual Studio 2012, download and install Update 2 that Microsoft released recently (as of 4/2013).

<a href="http://support.microsoft.com/kb/2797912" rel="nofollow">Visual Studio 2012 Update 2</a>

There are some bug fixes in that update related to the issue.

blocks|key|141284|text|有人说runAllManagedModulesForAllRequests=“真”会有性能问题和MVC路由问题。他们建议使用以下方法：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|141285|http://www.britishdeveloper.co.uk/2010/06/dont-use-modules-runallmanagedmodulesfo.html|offset|length|141286|http://bartwullems.blogspot.com/2012/06/optimize-performance-of-your-web.html|141287|entityMap|0|LINK|mutability|MUTABLE|url|1^0|0|0|2E|0|0|0|25|1|0^^$0|@$1|2|3|4|5|6|7|P|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|Q|8|@]|9|@$D|R|E|S|1|T]]|A|$]]|$1|F|3|G|5|6|7|U|8|@]|9|@$D|V|E|W|1|X]]|A|$]]|$1|H|3|-4|5|6|7|Y|8|@]|9|@]|A|$]]]|I|$J|$5|K|L|M|A|$N|C]]|O|$5|K|L|M|A|$N|G]]]]

Some people say runAllManagedModulesForAllRequests="true" will have performance issues and MVC routing issues.
They suggest to use the following:


 
 
 


<a href="http://www.britishdeveloper.co.uk/2010/06/dont-use-modules-runallmanagedmodulesfo.html" rel="nofollow">http://www.britishdeveloper.co.uk/2010/06/dont-use-modules-runallmanagedmodulesfo.html</a>

<a href="http://bartwullems.blogspot.com/2012/06/optimize-performance-of-your-web.html" rel="nofollow">http://bartwullems.blogspot.com/2012/06/optimize-performance-of-your-web.html</a>

blocks|key|359247|text|虽然标记的答案可以让它正常工作，但您真正需要添加到webconfig的是：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|359248|++++<handlers>
++++++
++++++<remove+name="UrlRoutingModule-4.0"/>
++++++
++++++<add+name="UrlRoutingModule-4.0"+path="*"+verb="*"+type="System.Web.Routing.UrlRoutingModule"+preCondition=""/>
++++</handlers>|code-block|syntax|javascript|359249|请注意，这些都没有特定的顺序，尽管您希望在添加之前删除。|359250|我们最终得到404的原因是因为Url路由模块只作用于IIS中网站的根目录。通过将模块添加到该应用程序的配置中，我们就拥有了在该应用程序的路径(子目录路径)下运行的模块，并且路由模块开始工作。|359251|entityMap^0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|M|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|N|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|O|8|@]|9|@]|A|$]]|$1|I|3|J|5|6|7|P|8|@]|9|@]|A|$]]|$1|K|3|-4|5|6|7|Q|8|@]|9|@]|A|$]]]|L|$]]

While the marked answer gets it working, all you really need to add to the webconfig is:

<pre><code> &lt;handlers&gt;
 &lt;!-- Your other remove tags--&gt;
 &lt;remove name="UrlRoutingModule-4.0"/&gt;
 &lt;!-- Your other add tags--&gt;
 &lt;add name="UrlRoutingModule-4.0" path="*" verb="*" type="System.Web.Routing.UrlRoutingModule" preCondition=""/&gt;
 &lt;/handlers&gt;
</code></pre>

Note that none of those have a particular order, though you want your removes before your adds.

The reason that we end up getting a 404 is because the Url Routing Module only kicks in for the root of the website in IIS. By adding the module to this application's config, we're having the module to run under this application's path (your subdirectory path), and the routing module kicks in.

blocks|key|141371|text|由于以下原因，也可能发生此问题|type|unstyled|depth|inlineStyleRanges|entityRanges|data|141372|1.在Web.Config中|141373|<system.webServer>
+++++<modules+runAllManagedModulesForAllRequests="true"+/>+
</system.webServer>|code-block|syntax|javascript|141374|2.确保以下内容在部署Web+API的服务器上的bin文件夹中可用|141375|·System.Net.Http|141376|·System.Net.Http.Formatting|141377|·System.Web.Http.WebHost|141378|·System.Web.Http|141379|如果通过Visual+Studio发布，则默认情况下不会将这些程序集复制到bin文件夹中，因为Web+API包是通过Nuget安装在开发计算机中的。但是，如果您希望将这些文件作为Visual+Studio发布的一部分提供，则需要将这些程序集的CopyLocal设置为True|141380|entityMap^0|0|0|0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|W|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|X|8|@]|9|@]|A|$]]|$1|D|3|E|5|F|7|Y|8|@]|9|@]|A|$G|H]]|$1|I|3|J|5|6|7|Z|8|@]|9|@]|A|$]]|$1|K|3|L|5|6|7|10|8|@]|9|@]|A|$]]|$1|M|3|N|5|6|7|11|8|@]|9|@]|A|$]]|$1|O|3|P|5|6|7|12|8|@]|9|@]|A|$]]|$1|Q|3|R|5|6|7|13|8|@]|9|@]|A|$]]|$1|S|3|T|5|6|7|14|8|@]|9|@]|A|$]]|$1|U|3|-4|5|6|7|15|8|@]|9|@]|A|$]]]|V|$]]

This issue can also happen due to the following 

1.In the Web.Config

<pre><code>&lt;system.webServer&gt;
 &lt;modules runAllManagedModulesForAllRequests="true" /&gt; 
&lt;/system.webServer&gt;
</code></pre>

2.Make sure the following are available in the bin folder on the server where the Web API is deployed

•System.Net.Http

•System.Net.Http.Formatting

•System.Web.Http.WebHost

•System.Web.Http

These assemblies won't be copied in the bin folder by default if the publish is through Visual Studio because the Web API packages are installed through Nuget in the development machine. Still if you want to achieve these files to be available as part of Visual Studio publish then you need to set CopyLocal to True for these Assemblies

blocks|key|141405|text|对我来说，除了拥有runAllManagedModulesForAllRequests="true"之外，我还必须编辑下面的"path"属性。以前，我的path属性是"*."，这意味着它只在包含点字符的url上执行。但是，我的应用程序的url不包含点。当我将路径切换到"*"时，它就起作用了。这是我现在所拥有的：|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|141406|++<system.webServer>
++++++<validation+validateIntegratedModeConfiguration="false"+/>
++++++<modules+runAllManagedModulesForAllRequests="true">
++++++<remove+name="WebDAVModule"/>
++++++</modules>

++++++<handlers>
++++++++++<remove+name="WebDAV"+/>
++++++++++<remove+name="ExtensionlessUrlHandler-ISAPI-4.0_32bit"+/>
++++++++++<remove+name="ExtensionlessUrlHandler-ISAPI-4.0_64bit"+/>
++++++++++<remove+name="ExtensionlessUrlHandler-Integrated-4.0"+/>
++++++++++<add+name="ExtensionlessUrlHandler-ISAPI-4.0_32bit"+path="*"+verb="*"+modules="IsapiModule"+scriptProcessor="%25windir%25\Microsoft.NET\Framework\v4.0.30319\aspnet_isapi.dll"+preCondition="classicMode,runtimeVersionv4.0,bitness32"+responseBufferLimit="0"+/>
++++++++++<add+name="ExtensionlessUrlHandler-ISAPI-4.0_64bit"+path="*"+verb="*"+modules="IsapiModule"+scriptProcessor="%25windir%25\Microsoft.NET\Framework64\v4.0.30319\aspnet_isapi.dll"+preCondition="classicMode,runtimeVersionv4.0,bitness64"+responseBufferLimit="0"+/>
++++++++++<add+name="ExtensionlessUrlHandler-Integrated-4.0"+path="*"+verb="*"+type="System.Web.Handlers.TransferRequestHandler"+preCondition="integratedMode,runtimeVersionv4.0"+/>
++++++</handlers>
++</system.webServer>|code-block|syntax|javascript|141407|entityMap^0|9|15|1Q|6|2B|4|3Q|3|0|0^^$0|@$1|2|3|4|5|6|7|M|8|@$9|N|A|O|B|C]|$9|P|A|Q|B|C]|$9|R|A|S|B|C]|$9|T|A|U|B|C]]|D|@]|E|$]]|$1|F|3|G|5|H|7|V|8|@]|D|@]|E|$I|J]]|$1|K|3|-4|5|6|7|W|8|@]|D|@]|E|$]]]|L|$]]

For me, in addition to having <code>runAllManagedModulesForAllRequests="true"</code> I also had to edit the <code>"path"</code>
attribute below. Previously my path attribute was <code>"*."</code> which means it only executed on url's containing a dot
character. However, my application's url's don't contain a dot. When I switched path to <code>"*"</code> then it worked.
Here's what I have now:

<pre><code> &lt;system.webServer&gt;
 &lt;validation validateIntegratedModeConfiguration="false" /&gt;
 &lt;modules runAllManagedModulesForAllRequests="true"&gt;
 &lt;remove name="WebDAVModule"/&gt;
 &lt;/modules&gt;

 &lt;handlers&gt;
 &lt;remove name="WebDAV" /&gt;
 &lt;remove name="ExtensionlessUrlHandler-ISAPI-4.0_32bit" /&gt;
 &lt;remove name="ExtensionlessUrlHandler-ISAPI-4.0_64bit" /&gt;
 &lt;remove name="ExtensionlessUrlHandler-Integrated-4.0" /&gt;
 &lt;add name="ExtensionlessUrlHandler-ISAPI-4.0_32bit" path="*" verb="*" modules="IsapiModule" scriptProcessor="%windir%\Microsoft.NET\Framework\v4.0.30319\aspnet_isapi.dll" preCondition="classicMode,runtimeVersionv4.0,bitness32" responseBufferLimit="0" /&gt;
 &lt;add name="ExtensionlessUrlHandler-ISAPI-4.0_64bit" path="*" verb="*" modules="IsapiModule" scriptProcessor="%windir%\Microsoft.NET\Framework64\v4.0.30319\aspnet_isapi.dll" preCondition="classicMode,runtimeVersionv4.0,bitness64" responseBufferLimit="0" /&gt;
 &lt;add name="ExtensionlessUrlHandler-Integrated-4.0" path="*" verb="*" type="System.Web.Handlers.TransferRequestHandler" preCondition="integratedMode,runtimeVersionv4.0" /&gt;
 &lt;/handlers&gt;
 &lt;/system.webServer&gt;
</code></pre>

blocks|key|141450|text|我已经和这个问题斗争了几天，尝试了所有建议的东西。我的dev机器工作得很好，但是我部署到的新机器出现了404错误。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|141451|在IIS管理器中，我比较了两台机器上的处理程序映射，发现缺少许多处理程序。原来这台机器上没有安装ASP.Net+5。|141452|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|F|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|G|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|H|8|@]|9|@]|A|$]]]|E|$]]

I have been battling this problem for a couple of days trying all kinds of things suggested. My dev machine was working fine, but the new machine I was deploying to was giving me the 404 error. 

In IIS manager, I compared the handler mappings on both machines to realize that a lot of handlers were missing. Turns out that ASP.Net 5 was not installed on the machine.

blocks|key|141520|text|对我来说，当我运行一个使用IIS+Express的应用程序时，在我的网站上收到了一个404错误:没有使用IIS+Express+(使用本地IIS)。如果我关闭用来运行IIS+Express的浏览器，那么404就会消失。对我来说，我让IIS+Express项目调用Local+IIS服务，所以我将IIS+Express项目转换为使用Local+IIS，然后一切都可以正常工作。由于某些原因，您似乎不能同时运行非IIS+Express和本地IIS网站。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|141521|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

For me I received a 404 error on my websites NOT using IIS Express (using Local IIS) while running an application that WAS using IIS Express. If I would close the browser that was used to run IIS Express, then the 404 would go away. For me I had my IIS Express project calling into Local IIS services, so I converted the IIS Express project to use Local IIS and then everything worked. It seems that you can't run both a non-IIS Express and Local IIS website at the same time for some reason.

blocks|key|359413|text|我在Blazor上遇到了这个问题，我发现在我对控制器的调用中加入了NavManagers+"baseUrl“就解决了这个问题，而不管是使用虚拟目录还是根网站。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|359414|这对我很有效！|359415|string+baseUrl+=+NavigationManager.BaseUri.ToString();

NavigationManager.NavigateTo(**baseUrl**+%2B+$"api/Download/DownloadFile?FileName="+%2B+sFilename,+true);|code-block|syntax|javascript|359416|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|K|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|L|8|@]|9|@]|A|$]]|$1|D|3|E|5|F|7|M|8|@]|9|@]|A|$G|H]]|$1|I|3|-4|5|6|7|N|8|@]|9|@]|A|$]]]|J|$]]

I had this problem with Blazor and found that incorporating NavManagers &quot;baseUrl&quot; into my calls to the controller solved the issue regardless of using a Virtual Directory or the root website.
This worked for me!
<pre class="lang-cs prettyprint-override"><code>string baseUrl = NavigationManager.BaseUri.ToString();

NavigationManager.NavigateTo(**baseUrl** + $&quot;api/Download/DownloadFile?FileName=&quot; + sFilename, true);
</code></pre>

I have an ASP.NET Web API which works fine when running on "IIS Express" with localhost:1783

<img src="https://i.stack.imgur.com/dvgor.png" alt="Settings in VS">

But when I uncross the "Use IIS Express" and then press "Create Virtual Directory"...

<img src="https://i.stack.imgur.com/edHZp.png" alt="New settings">

...I just get 404 errors:
<img src="https://i.stack.imgur.com/jhcWf.png" alt="The 404 error">

Any ideas whats wrong? Thanks!

ASP.NET Web API application gives 404 when deployed at IIS 7

Visual Studio

服务器

路由

我有一个IIS Web API，它在"IIS Express“上运行时工作良好，本地主机为:1783​​但是当我打开“使用IIS Express”，然后按下“创建虚拟目录”...​​...I只得到了404个错误：​你知道怎么回事吗？谢谢!

问ASP.NET Web API应用程序在IIS7上部署时提供404
EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问ASP.NET Web API应用程序在IIS7上部署时提供404EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问ASP.NET Web API应用程序在IIS7上部署时提供404
EN