blocks|key|181560|text|问题出在您的路由配置中。Mvc路由不同于WebApi路由。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|181561|添加对System.Web.Http.dll、System.Web.Http.Webhost.dll、System.Net.Http.dll的引用，配置您的接口路由，如下所示：|181562|+++GlobalConfiguration.Configuration.Routes.MapHttpRoute(
+++++name:+"DefaultApi",
+++++routeTemplate:+"api/{controller}/{id}",
+++++defaults:+new+{+id+=+System.Web.Http.RouteParameter.Optional+}
+++);|code-block|syntax|javascript|181563|entityMap^0|C|3|K|6|0|3|J|N|R|1F|J|0|0^^$0|@$1|2|3|4|5|6|7|O|8|@$9|P|A|Q|B|C]|$9|R|A|S|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|T|8|@$9|U|A|V|B|C]|$9|W|A|X|B|C]|$9|Y|A|Z|B|C]]|D|@]|E|$]]|$1|H|3|I|5|J|7|10|8|@]|D|@]|E|$K|L]]|$1|M|3|-4|5|6|7|11|8|@]|D|@]|E|$]]]|N|$]]

The problem is in your routing configuration. <code>Mvc</code> routing is different from <code>WebApi</code> routing.

Add reference to <code>System.Web.Http.dll</code>, <code>System.Web.Http.Webhost.dll</code> and <code>System.Net.Http.dll</code> and then configure your API routing as follows: 

<pre><code> GlobalConfiguration.Configuration.Routes.MapHttpRoute(
 name: "DefaultApi",
 routeTemplate: "api/{controller}/{id}",
 defaults: new { id = System.Web.Http.RouteParameter.Optional }
 );
</code></pre>

blocks|key|4687610|text|请确保以下事项|type|unstyled|depth|inlineStyleRanges|entityRanges|data|4687611|1.)如果您的web+api是4.5，请确保已使用.NET+4.5或4.0配置了IIS。在IIS中安装4.5|4687612|使用管理员权限在命令提示符下运行此命令|4687613|C:\Windows\Microsoft.NET\Framework\v4.0.30319>aspnet_regiis.exe+-i|code-block|syntax|javascript|4687614|2.)将您的路由更改为|4687615|RouteTable.Routes.MapHttpRoute(
++++++name:+"DefaultApi",
++++++routeTemplate:+"{controller}/{id}",
++++++defaults:+new+{+id+=+System.Web.Http.RouteParameter.Optional+}
+);|4687616|并使用Demo/Get发出请求(其中demo是您的控制器名称)|4687617|如果%251、%252不工作，请尝试%253|4687618|3.)在web.config文件中添加以下配置|4687619|<system.webServer>
++++<modules+runAllManagedModulesForAllRequests="true"+/>

</system.webServer>|4687620|entityMap^0|0|0|0|0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|Y|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|Z|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|10|8|@]|9|@]|A|$]]|$1|F|3|G|5|H|7|11|8|@]|9|@]|A|$I|J]]|$1|K|3|L|5|6|7|12|8|@]|9|@]|A|$]]|$1|M|3|N|5|H|7|13|8|@]|9|@]|A|$I|J]]|$1|O|3|P|5|6|7|14|8|@]|9|@]|A|$]]|$1|Q|3|R|5|6|7|15|8|@]|9|@]|A|$]]|$1|S|3|T|5|6|7|16|8|@]|9|@]|A|$]]|$1|U|3|V|5|H|7|17|8|@]|9|@]|A|$I|J]]|$1|W|3|-4|5|6|7|18|8|@]|9|@]|A|$]]]|X|$]]

Ensure the following things

1.) Ensure that your IIS is configured with .NET 4.5 or 4.0 if your web api is 4.5 install 4.5 in IIS 

run this command in command prompt with administrator privilege

<pre><code>C:\Windows\Microsoft.NET\Framework\v4.0.30319&gt;aspnet_regiis.exe -i
</code></pre>

2.) Change your routing to 

<pre><code>RouteTable.Routes.MapHttpRoute(
 name: "DefaultApi",
 routeTemplate: "{controller}/{id}",
 defaults: new { id = System.Web.Http.RouteParameter.Optional }
 );
</code></pre>

and make request with Demo/Get (where demo is your controller name)

if the 1,2 are not working try 3

3.) Add following configuration in web.config file

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

&lt;/system.webServer&gt;
</code></pre>

blocks|key|181647|text|您的路由配置看起来不错。仔细检查web.config中的处理程序部分，对于集成模式，这是使用ExtensionLessUrlHandler的正确方式：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|181648|<add+name="ExtensionlessUrlHandler-Integrated-4.0"+path="*."+verb="GET,HEAD,POST,DEBUG,PUT,DELETE,PATCH,OPTIONS"+type="System.Web.Handlers.TransferRequestHandler"+preCondition="integratedMode,runtimeVersionv4.0"+/>|code-block|syntax|javascript|181649|有关此主题的更多信息：http://blogs.msdn.com/b/tmarq/archive/2010/05/26/how-extensionless-urls-are-handled-by-asp-net-v4.aspx|offset|length|181650|entityMap|0|LINK|mutability|MUTABLE|url|http://blogs.msdn.com/b/tmarq/archive/2010/05/26/how-extensionless-urls-are-handled-by-asp-net-v4.aspx^0|0|0|B|2U|0|0^^$0|@$1|2|3|4|5|6|7|S|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|T|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|U|8|@]|9|@$I|V|J|W|1|X]]|A|$]]|$1|K|3|-4|5|6|7|Y|8|@]|9|@]|A|$]]]|L|$M|$5|N|O|P|A|$Q|R]]]]

Your route configuration looks good. Double check the handlers section in web.config, for integrated mode this is the proper way to use ExtensionLessUrlHandler:

<pre><code>&lt;add name="ExtensionlessUrlHandler-Integrated-4.0" path="*." verb="GET,HEAD,POST,DEBUG,PUT,DELETE,PATCH,OPTIONS" type="System.Web.Handlers.TransferRequestHandler" preCondition="integratedMode,runtimeVersionv4.0" /&gt;
</code></pre>

More on this topic:
<a href="http://blogs.msdn.com/b/tmarq/archive/2010/05/26/how-extensionless-urls-are-handled-by-asp-net-v4.aspx" rel="nofollow">http://blogs.msdn.com/b/tmarq/archive/2010/05/26/how-extensionless-urls-are-handled-by-asp-net-v4.aspx</a>

blocks|key|4687684|text|如果您在App_Code中创建控制器，路由表如何知道它在哪里？您已指定路由为"api/{controller/...“但这不是控制器所在的位置。尝试将其移动到正确的文件夹中。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|4687685|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|$]]

If you create the controller in App_Code how does the routing table know where it is? You have specified the route as "api/{controller/..." but that's not where the controller is located. Try moving it into the correct folder.

blocks|key|181698|text|另外，确保您的控制器以名称"+controller“结尾，如"PizzaPieController”。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|181699|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|$]]

Also, make sure your controller ends in the name "Controller" as in "PizzaPieController".

blocks|key|4687752|text|我正在经历这个问题。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|4687753|我尝试编辑我的WebApiConfig.cs，以满足这里的一些建议和其他地方的代码示例。有些工作了，但它没有解释为什么当WebApiConfig.cs完全按照MS模板WebApi项目编码时，路由不能工作。|offset|length|style|CODE|4687754|我的实际问题是，在手动将WebApi添加到项目中时，我没有遵循来自Global.asax的配置调用的常用顺序|4687755|++++protected+void+Application_Start()
++++{
++++++++AreaRegistration.RegisterAllAreas();
++++++++//+This+is+where+it+"should"+be
++++++++GlobalConfiguration.Configure(WebApiConfig.Register);
++++++++FilterConfig.RegisterGlobalFilters(GlobalFilters.Filters);
++++++++RouteConfig.RegisterRoutes(RouteTable.Routes);
++++++++//+The+WebApi+routes+cannot+be+initialized+here.
++++++++BundleConfig.RegisterBundles(BundleTable.Bundles);
++++}|code-block|syntax|javascript|4687756|我可以猜测为什么会这样，但我没有进一步调查。至少可以说，这是不直观的。|4687757|entityMap^0|0|7|F|1O|F|0|C|6|X|B|0|0|0^^$0|@$1|2|3|4|5|6|7|S|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|T|8|@$D|U|E|V|F|G]|$D|W|E|X|F|G]]|9|@]|A|$]]|$1|H|3|I|5|6|7|Y|8|@$D|Z|E|10|F|G]|$D|11|E|12|F|G]]|9|@]|A|$]]|$1|J|3|K|5|L|7|13|8|@]|9|@]|A|$M|N]]|$1|O|3|P|5|6|7|14|8|@]|9|@]|A|$]]|$1|Q|3|-4|5|6|7|15|8|@]|9|@]|A|$]]]|R|$]]

I was experiencing this problem.

I tried editing my <code>WebApiConfig.cs</code> to meet a number of recommendations here and code samples elsewhere. Some worked, but it didn't explain to why the route was not working when <code>WebApiConfig.cs</code> was coded exactly as per the MS template WebApi project.

My actual problem was that in manually adding <code>WebApi</code> to my project, I had not followed the stock order of configuration calls from <code>Global.asax</code>

<pre><code> protected void Application_Start()
 {
 AreaRegistration.RegisterAllAreas();
 // This is where it "should" be
 GlobalConfiguration.Configure(WebApiConfig.Register);
 FilterConfig.RegisterGlobalFilters(GlobalFilters.Filters);
 RouteConfig.RegisterRoutes(RouteTable.Routes);
 // The WebApi routes cannot be initialized here.
 BundleConfig.RegisterBundles(BundleTable.Bundles);
 }
</code></pre>

I could make guesses about why this is, but I didn't investigate further. It wasn't intuitive to say the least.

blocks|key|181773|text|我尝试了上面所有的方法，也遇到了同样的问题。原来，在IIS2.0中创建的应用程序池默认为.net+2.0。当我将其更改为4.0时，它又可以工作了|type|unstyled|depth|inlineStyleRanges|entityRanges|data|181774|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|$]]

I tried all of the above and had the same problem. It turned out that the App pool created in IIS defaulted to .net 2.0. When I changed it to 4.0 then it worked again

blocks|key|181805|text|同时尝试删除整个api+bin文件夹的内容。我的是包含旧的dll(由于一个大的命名空间重命名)，暴露了冲突的控制器。这些dll没有被Visual+Studio的Clean功能删除。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|181806|(然而，我发现asp.net+web+api严重缺乏调试级别的路由和调试信息)。|181807|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|$]]

Also try to delete your entire api bin folder's content. Mine was containing old dlls (due to a big namespace renaming) exposing conflicting controllers. Those dll weren't deleted by Visual Studio's Clean functionality.

(However, I find asp.net web api seriously lacks routing and debugging information at the debugging level).

blocks|key|4687841|text|上面的解决方案都没有解决我的问题。我的错误是我直接将bin文件复制到生产服务器，然后我就不工作了。当我将项目发布到磁盘并将“发布的”文件夹复制到服务器时，404已经消失了。这有点明显，但是，可以帮助一些人。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|4687842|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|$]]

None of solutions above solved my problem... My error was that I copied the bin files directly to production server, and then, I don't work. The 404 was gone when I publish the project to disk and copied the "published" folder to server. It's a little obvious, but, can help some one.

blocks|key|181873|text|是时候把我的愚蠢疏忽添加到这里的列表中了:我错误地输入了我的webapi默认路由路径。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|181874|原件：|181875|config.Routes.MapHttpRoute(
++++++++++++name:+"DefaultApi",
++++++++++++routeTemplate:+"api/{controller}/id",
++++++++++++defaults:+new+{+id+=+RouteParameter.Optional}
++++++++);|code-block|syntax|javascript|181876|已修复：(注意“id”周围的花括号)|181877|config.Routes.MapHttpRoute(
++++++++++++name:+"DefaultApi",
++++++++++++routeTemplate:+"api/{controller}/{id}",
++++++++++++defaults:+new+{+id+=+RouteParameter.Optional}
++++++++);|181878|entityMap^0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|O|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|P|8|@]|9|@]|A|$]]|$1|D|3|E|5|F|7|Q|8|@]|9|@]|A|$G|H]]|$1|I|3|J|5|6|7|R|8|@]|9|@]|A|$]]|$1|K|3|L|5|F|7|S|8|@]|9|@]|A|$G|H]]|$1|M|3|-4|5|6|7|T|8|@]|9|@]|A|$]]]|N|$]]

Time for me to add my silly oversight to the list here: I mistyped my webapi default route path.

Original:

<pre><code>config.Routes.MapHttpRoute(
 name: "DefaultApi",
 routeTemplate: "api/{controller}/id",
 defaults: new { id = RouteParameter.Optional}
 );
</code></pre>

Fixed: (observe the curly braces around "id")

<pre><code>config.Routes.MapHttpRoute(
 name: "DefaultApi",
 routeTemplate: "api/{controller}/{id}",
 defaults: new { id = RouteParameter.Optional}
 );
</code></pre>

blocks|key|181903|text|我将一个基于RouteAttribute的控制器dll复制到了bin文件夹中，但是它没有被识别为有效的控制器，并且我在客户机上得到了404错误。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|181904|经过多次调试，我发现了我的问题。这是因为控制器引用的System.Web.Http.dll版本与主项目(包含global.asax.cs的项目)引用的System.Web.Http.dll版本不同。|181905|Asp.Net使用如下代码通过反射找到控制器|181906|internal+static+bool+IsControllerType(Type+t)
{
++++return
++++++++t+!=+null+&&
++++++++t.IsClass+&&
++++++++t.IsVisible+&&
++++++++!t.IsAbstract+&&
++++++++typeof(IHttpController).IsAssignableFrom(t)+&&
++++++++HasValidControllerName(t);
}|code-block|syntax|javascript|181907|由于每个版本的System.Web.Http.dll的IHttpController都不同，因此控制器和主项目必须具有相同的引用。|181908|entityMap^0|6|E|0|Q|J|23|J|0|0|0|7|J|R|F|0^^$0|@$1|2|3|4|5|6|7|S|8|@$9|T|A|U|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|V|8|@$9|W|A|X|B|C]|$9|Y|A|Z|B|C]]|D|@]|E|$]]|$1|H|3|I|5|6|7|10|8|@]|D|@]|E|$]]|$1|J|3|K|5|L|7|11|8|@]|D|@]|E|$M|N]]|$1|O|3|P|5|6|7|12|8|@$9|13|A|14|B|C]|$9|15|A|16|B|C]]|D|@]|E|$]]|$1|Q|3|-4|5|6|7|17|8|@]|D|@]|E|$]]]|R|$]]

I copied a <code>RouteAttribute</code> based controller dll into the bin folder, but it wasn't getting recognized as a valid controller and I was getting the 404 error on the client.

After much debugging, I found my problem. It was because the version of <code>System.Web.Http.dll</code> that the controller was referencing was different from the version of <code>System.Web.Http.dll</code> that the main project (the one containing global.asax.cs) was referencing.

Asp.Net finds the controller by reflection using code like this

<pre><code>internal static bool IsControllerType(Type t)
{
 return
 t != null &amp;&amp;
 t.IsClass &amp;&amp;
 t.IsVisible &amp;&amp;
 !t.IsAbstract &amp;&amp;
 typeof(IHttpController).IsAssignableFrom(t) &amp;&amp;
 HasValidControllerName(t);
}
</code></pre>

Since <code>IHttpController</code> is different for each version of <code>System.Web.Http.dll</code>, the controller and the main project have to have the same reference.

blocks|key|181919|text|我们也有这个问题，将.NET版本从4.5改为4.5.1或更高版本解决了这个问题|type|unstyled|depth|inlineStyleRanges|entityRanges|data|181920|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|$]]

We had this as well, changing .NET version from 4.5 to 4.5.1 or newer solved the issue

blocks|key|181931|text|谢谢香农，工作很棒=>|type|unstyled|depth|inlineStyleRanges|entityRanges|data|181932|我在Global.asax中的顺序是：|181933|GlobalConfiguration.Configure(WebApiConfig.Register);++
RouteConfig.RegisterRoutes(RouteTable.Routes);|code-block|syntax|javascript|181934|而不是好的：|181935|RouteConfig.RegisterRoutes(RouteTable.Routes);
GlobalConfiguration.Configure(WebApiConfig.Register);+|181936|entityMap^0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|O|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|P|8|@]|9|@]|A|$]]|$1|D|3|E|5|F|7|Q|8|@]|9|@]|A|$G|H]]|$1|I|3|J|5|6|7|R|8|@]|9|@]|A|$]]|$1|K|3|L|5|F|7|S|8|@]|9|@]|A|$G|H]]|$1|M|3|-4|5|6|7|T|8|@]|9|@]|A|$]]]|N|$]]

Thanks Shannon, works great =>

My order in my Global.asax was :

<pre><code>GlobalConfiguration.Configure(WebApiConfig.Register); 
RouteConfig.RegisterRoutes(RouteTable.Routes);
</code></pre>

instead of the good one : 

<pre><code>RouteConfig.RegisterRoutes(RouteTable.Routes);
GlobalConfiguration.Configure(WebApiConfig.Register); 
</code></pre>

blocks|key|181986|text|我感谢这是一个非常老的问题，但我想我会为未来的用户添加另一个答案。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|181987|我刚刚发现，在我工作的一个项目中，只有在将其部署到CI/Staging之后，才会发生这种情况。解决方案是在将每个版本部署到每个环境一次的同时来回切换编译debug=的“true”值，它会自动为我修复。|181988|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 appreciate this is a very old question but I thought I would add another answer for future users.

I found this to happen just now in a project I was working on only after it was deployed to CI/Staging. The solution was to toggle the compilation debug="true" value back and forth while deploying each version to each environment once, and it would fix itself for me.

blocks|key|4688004|text|在我的例子中，我忘了让它从ApiController派生出来。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|4688005|所以看起来就像|4688006|public+class+ValuesController+:+ApiController|code-block|syntax|javascript|4688007|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|$]]

In my case I forgot to make it derive from ApiController. 

So it would look like 

<pre><code>public class ValuesController : ApiController
</code></pre>

blocks|key|4688031|text|注册路由的顺序是我的Application_Start()中的问题。对我有效的序列是|type|unstyled|depth|inlineStyleRanges|entityRanges|data|4688032|AreaRegistration.RegisterAllAreas();
GlobalConfiguration.Configure(WebApiConfig.Register);
RouteConfig.RegisterRoutes(RouteTable.Routes);|code-block|syntax|javascript|4688033|早些时候是|4688034|AreaRegistration.RegisterAllAreas();
RouteConfig.RegisterRoutes(RouteTable.Routes);
GlobalConfiguration.Configure(WebApiConfig.Register);|4688035|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|D|7|P|8|@]|9|@]|A|$E|F]]|$1|K|3|-4|5|6|7|Q|8|@]|9|@]|A|$]]]|L|$]]

The sequence of registering the route, was the issue in my Application_Start().
the sequence which worked for me was 

<pre><code>AreaRegistration.RegisterAllAreas();
GlobalConfiguration.Configure(WebApiConfig.Register);
RouteConfig.RegisterRoutes(RouteTable.Routes);
</code></pre>

earlier it was

<pre><code>AreaRegistration.RegisterAllAreas();
RouteConfig.RegisterRoutes(RouteTable.Routes);
GlobalConfiguration.Configure(WebApiConfig.Register);
</code></pre>

I have an asp.net web forms application running under v4.0 integrated mode.

I tried to add an apicontroller in the App_Code folder. 

In the Global.asax, I added the following code

<pre><code> RouteTable.Routes.MapHttpRoute(
 name: "DefaultApi",
 routeTemplate: "api/{controller}/{id}",
 defaults: new { id = System.Web.Http.RouteParameter.Optional }
 );
</code></pre>

When I tried to navigate to the controller at <code>http://localhost/api/Value</code>, I get the 404 error.

The extensionless url is configured in the handler section. I have forms and anonymous authentication enabled for the website. 

ExtensionLess url is configured for '*.'

When I hit the url for controller, the request is handled by StaticHandler instead of ExtensionlessUrlHandler-Integrated-4.0. 

I have no clue now why the system will throw the error as shown in the image below.
<img src="https://i.stack.imgur.com/Y9s0C.png" alt="Error">

ASP.NET MVC WebAPI 404 error

Visual Studio

身份验证

服务器

Windows

路由

我有一个在v4.0集成模式下运行的asp.net web forms应用程序。我尝试在App_Code文件夹中添加一个apicontroller。在Global.asax中，我添加了以下代码 RouteTable.Routes.MapHttpRoute(      name: "DefaultApi",      ro...

问ASP.NET MVC WebAPI 404错误
EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问ASP.NET MVC WebAPI 404错误EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问ASP.NET MVC WebAPI 404错误
EN