我在同一控制器上有两个动作,具有相同的路由,但有单独的HttpMethod
要求(POST
与DELETE
)。
[AllowAnonymous]
public class TestController : ApiController
{
[Route("~/api/test")]
[HttpDelete]
public IHttpActionResult Endpoint1()
{
return this.Ok("endpoint1");
}
[Route("~/api/test")]
[HttpPost]
public IHttpActionResult Endpoint2()
{
return this.Ok("endpoint2");
}
}
这很好-从DELETE
切换到POST
时,两个端点都可以工作。
例如
DELETE /api/test = endpoint1
POST /api/test = endpoint2
如果我将动作分成单独的控制器,它将不再起作用:
[AllowAnonymous]
public class TestController : ApiController
{
[Route("~/api/test")]
[HttpDelete]
public IHttpActionResult Endpoint1()
{
return this.Ok("endpoint1");
}
}
[AllowAnonymous]
public class TestController2 : ApiController
{
[Route("~/api/test")]
[HttpPost]
public IHttpActionResult Endpoint2()
{
return this.Ok("endpoint2");
}
}
例如
DELETE /api/test = endpoint1
POST /api/test = { "Message": "The requested resource does not support http method 'POST'." }
这是应该从框架中获得的吗?
编辑:确切的WebAPI软件包版本为:5.2.3
Web API 2.0不允许路由在两个不同的控制器上匹配。这在MVC 6(Web API组合框架)中得以解决。
首先像@woogy,然后您说,这不是很常见的模式,所以大多数用户不应该去这里(或在RTM上转至MVC 6)。
根本原因是路由实际匹配,定义为IActionHttpMethodProvider
的动词不限制路由匹配,并且它在多个控制器上匹配,因此失败。
但是,您可以在路径上定义约束,并且副作用是获得了更简洁的API。
这将限制路由以仅匹配预定义的动词,因此它将不匹配其他控制器。
public class VerbConstraint : IHttpRouteConstraint
{
private HttpMethod _method;
public VerbConstraint(HttpMethod method)
{
_method = method;
}
public bool Match(HttpRequestMessage request,
IHttpRoute route,
string parameterName,
IDictionary<string, object> values,
HttpRouteDirection routeDirection)
{
// Note - we only want to constraint on the outgoing path
if (routeDirection == HttpRouteDirection.UriGeneration ||
request.Method == _method)
{
return true;
}
return false;
}
}
public abstract class VerbRouteAttribute : RouteFactoryAttribute, IActionHttpMethodProvider
{
private string _template;
private HttpMethod _method;
public VerbRouteAttribute(string template, string verb)
: base(template)
{
_method = new HttpMethod(verb);
}
public Collection<HttpMethod> HttpMethods
{
get
{
var methods = new Collection<HttpMethod>();
methods.Add(_method);
return methods;
}
}
public override IDictionary<string, object> Constraints
{
get
{
var constraints = new HttpRouteValueDictionary();
constraints.Add("verb", new VerbConstraint(_method));
return constraints;
}
}
}
该课程合并了三件事1.带有路由模板的路由属性2.将动词路由约束应用于路由3.指定操作方法选择器,以便系统的其余部分(如帮助页面)可以像[HttpPost]
/ [HttpDelete]
public class PostRouteAttribute : VerbRouteAttribute
{
public PostRouteAttribute(string template) : base(template, "POST")
{
}
}
public class DeleteRouteAttribute : VerbRouteAttribute
{
public DeleteRouteAttribute(string template) : base(template, "DELETE")
{
}
}
您所知道的这些都是微不足道的,只需在代码中更平滑地使用这些属性即可。
[AllowAnonymous]
public class TestController : ApiController
{
[DeleteRoute("api/test")]
public IHttpActionResult Endpoint1()
{
return this.Ok("endpoint1");
}
}
[AllowAnonymous]
public class TestController2 : ApiController
{
[PostRoute("api/test")]
public IHttpActionResult Endpoint2()
{
return this.Ok("endpoint2");
}
}
[HttpDelete(“ DeleteEmployee / {id}”)]公共异步任务DeleteEmployee(Guid id)