自定義路由處理程序

Question

我能夠成功註冊內的global.asax.cs自定義的路由處理（從IRouteHandler導出）爲Web API路線ALA：

 routes.MapHttpRoute(
      name: "DefaultApi", 
      routeTemplate: "{client}/api/1.0/{controller}/{action}/{id}", 
      defaults: new{id = UrlParameter.Optional} 
     ).RouteHandler = new SingleActionAPIRouteHandler(); 

不過，我可以在嘗試爲集成測試API設置內存主機時，似乎找不到方法來執行此操作，當我調用HttpConfiguration.Routes.MapRoute時，我無法在返回的IHttpRoute上設置處理程序。

我應該這樣做不同（例如通過使用自定義的HttpControllerSelector）？我顯然希望在兩種情況下都以同樣的方式進行。

謝謝， 馬特

編輯：

所以我落得這樣做基本上採取從下面的建議，而是簡單地重寫HttpControllerDispatcher類，如下所示：

public class CustomHttpControllerDispatcher : HttpControllerDispatcher 
{ 
    public CustomHttpControllerDispatcher(HttpConfiguration configuration) : base(configuration) 
    { 
    } 
    protected override Task<HttpResponseMessage> SendAsync(HttpRequestMessage request, CancellationToken cancellationToken) 
    { 
     // My stuff here 

     return base.SendAsync(request, cancellationToken); 
    } 
} 

Answer 1

你是非常正確。自主主機返回IHttpRoute並將HttpMessageHandler作爲參數。似乎沒有內在的方式來專門化路由處理程序。

更新：要成爲一個更清楚一點

你應該幾乎可以肯定在利用旅途中HttpControllerSelector並實現自定義的一個...一個例子是。 http://netmvc.blogspot.co.uk/

下面是一個實驗位的，如果HttpControllerSelector不sufficent您對什麼都要求原因...

但是，正如你可以看到MapHttpRoute確實有HttpMessageHandler過載，所以你可以試驗這個... if the handler is NULL then it defaults to IHttpController，但你可以實現你自己的，並使用它來指揮正確的控制器... MVC框架似乎使用[HttpControllerDispatcher]here，所以借用一些代碼，你可以在這裏放置自己的控制器/路由選擇代碼您也可以訪問路線和選擇器，並可以自行調換。

這CustomHttpControllerDispatcher代碼是DEMO只...查找線路

//做一些定製來接你的控制器

也許有一個遊戲...

實施例路線：

 config.Routes.MapHttpRoute(
      name: "DefaultApi", 
      routeTemplate: "api/{controller}/{id}", 
      defaults: new { id = RouteParameter.Optional }, 
      constraints: null, 
      handler: new CustomHttpControllerDispatcher(config) 
     ); 

例CustomHttpControllerDispatcher：

public class CustomHttpControllerDispatcher : HttpMessageHandler 
{ 
     private IHttpControllerSelector _controllerSelector; 
     private readonly HttpConfiguration _configuration; 

     public CustomHttpControllerDispatcher(HttpConfiguration configuration) 
     { 
      _configuration = configuration; 
     } 

     public HttpConfiguration Configuration 
     { 
      get { return _configuration; } 
     } 

     private IHttpControllerSelector ControllerSelector 
     { 
      get 
      { 
       if (_controllerSelector == null) 
       { 
        _controllerSelector = _configuration.Services.GetHttpControllerSelector(); 
       } 
       return _controllerSelector; 
      } 
     } 

     protected override Task<HttpResponseMessage> SendAsync(HttpRequestMessage request, CancellationToken cancellationToken) 
     { 
       return SendAsyncInternal(request, cancellationToken); 
     } 

     private Task<HttpResponseMessage> SendAsyncInternal(HttpRequestMessage request, CancellationToken cancellationToken) 
     { 

      IHttpRouteData routeData = request.GetRouteData(); 
      Contract.Assert(routeData != null); 

      //DO SOMETHING CUSTOM HERE TO PICK YOUR CONTROLLER 
      HttpControllerDescriptor httpControllerDescriptor = ControllerSelector.SelectController(request); 
      IHttpController httpController = httpControllerDescriptor.CreateController(request); 

      // Create context 
      HttpControllerContext controllerContext = new HttpControllerContext(_configuration, routeData, request); 
      controllerContext.Controller = httpController; 
      controllerContext.ControllerDescriptor = httpControllerDescriptor; 

      return httpController.ExecuteAsync(controllerContext, cancellationToken); 
     } 
}