asp.net-mvc – 添加ELMAH并更改elmah.mvc.route后,旧路由仍然可

routes.MapRoute(
        "Default",// Route name
        "{controller}/{action}/{id}",// URL with parameters
        new { controller = "Home",action = "Index",id = UrlParameter.Optional });

无论您是否想要,路线的“{controller}”部分都会找到匹配的控制器.在这种情况下,这显然是有问题的.

您可以使用IRouteConstraint(概述为here)在路由上添加约束.NotEqual约束实际上非常有用.

using System;
using System.Web;
using System.Web.Routing;

public class NotEqual : IRouteConstraint
{
    private string _match = String.Empty;

    public NotEqual(string match)
    {
        _match = match;
    }

    public bool Match(HttpContextBase httpContext,Route route,string parameterName,RouteValueDictionary values,RouteDirection routeDirection)
    {
        return String.Compare(values[parameterName].ToString(),_match,true) != 0;
    }
}

因此,使用以下内容将ElmahController从默认路由中排除.

routes.MapRoute(
        "Default",id = UrlParameter.Optional },new { controller = new NotEqual("Elmah") });

这将使“/ elmah”的请求返回404.