MVC 5如何與本地化路線

Question

定義Owin LOGINPATH我有一個MVC 5網站提供本地化航線"en-US"定義爲

routes.MapRoute(
      name: "Default", 
      url: "{culture}/{controller}/{action}/{id}", 
      defaults: new { culture = CultureHelper.GetDefaultCulture(), controller = "Home", action = "Index", id = UrlParameter.Optional } 
     ); 

其中默認的培養結果。

---

問題出現在啓動時，我有使用LOGINPATH屬性來定義登錄URL，它被設置一次，它總是會使用提供的值，例如如果「/ zh-cn/Account/Login」是指定值，則爲默認文化。然後，我嘗試使用UrlHelper類的經驗，一些神奇的希望，但結果顯然是相同的：

var httpContext = HttpContext.Current; 
     if (httpContext == null) { 
      var request = new HttpRequest("/", "http://example.com", ""); 
      var response = new HttpResponse(new StringWriter()); 
      httpContext = new HttpContext(request, response); 
     } 

     var httpContextBase = new HttpContextWrapper(httpContext); 
     var routeData = new RouteData(); 
     var requestContext = new RequestContext(httpContextBase, routeData); 
     UrlHelper helper = new UrlHelper(requestContext); 

     var loginPath = helper.Action("Login", "Account"); 

     // Enable the application to use a cookie to store information for the signed in user 
     app.UseCookieAuthentication(new CookieAuthenticationOptions 
     { 
      AuthenticationType = DefaultAuthenticationTypes.ApplicationCookie,     
      LoginPath = new PathString(loginPath) 
     }); 

我的問題是：有沒有辦法破解這個機制來動態檢索當前文化還是我我被迫將當前文化設置爲cookie，並且當我重定向到登錄頁面時，在呈現頁面之前使用cookie值設置當前文化？

謝謝

Answer 1

我完全有同樣的問題，並想出了一種方法來克服這種限制。

在CookieAuthenticationOptions選項中，有一個「Provider」屬性，它使用CookieAuthenticationProvider進行初始化。這實現了一種稱爲ApplyRedirect的方法和一個代表OnApplyRedirect。 我的第一個想法是覆蓋此ApplyRedirect並實現處理本地化路由所需的邏輯。但不幸的是它不能被覆蓋。將我的邏輯傳遞給OnApplyRedirect會導致覆蓋默認行爲。理論上你可以抓住source of this behavior，將它複製到你的項目中並根據需要進行修改，但這顯然不是一個好習慣。 首先，我決定圍繞CookieAuthenticationProvider使用委託並使用兩個擴展點創建一個包裝，並保留默認行爲，除了使用的url或更容易的解決方法（thx to lafi）。

然後在身份驗證的配置我將我的自定義邏輯供應商：

public void ConfigureAuth(IAppBuilder app) 
{ 
    UrlHelper url = new UrlHelper(HttpContext.Current.Request.RequestContext); 

    CookieAuthenticationProvider provider = new CookieAuthenticationProvider(); 

    var originalHandler = provider.OnApplyRedirect; 

    //Our logic to dynamically modify the path (maybe needs some fine tuning) 
    provider.OnApplyRedirect = context => 
    { 
     var mvcContext = new HttpContextWrapper(HttpContext.Current); 
     var routeData = RouteTable.Routes.GetRouteData(mvcContext); 

     //Get the current language 
     RouteValueDictionary routeValues = new RouteValueDictionary(); 
     routeValues.Add("lang", routeData.Values["lang"]); 

     //Reuse the RetrunUrl 
     Uri uri = new Uri(context.RedirectUri); 
     string returnUrl = HttpUtility.ParseQueryString(uri.Query)[context.Options.ReturnUrlParameter]; 
     routeValues.Add(context.Options.ReturnUrlParameter, returnUrl); 

     //Overwrite the redirection uri 
     context.RedirectUri = url.Action("login", "account", routeValues); 
     originalHandler.Invoke(context); 
    }; 

    app.UseCookieAuthentication(new CookieAuthenticationOptions 
    { 
     AuthenticationType = DefaultAuthenticationTypes.ApplicationCookie, 
     LoginPath = new PathString(url.Action("login", "account")), 
     //Set the Provider 
     Provider = provider 
    }); 
} 

參見下面的代碼：

• CookieAuthenticationHandler
• CookieAuthenticationProvider

希望它適合您的需求。

UPDATE： 對於減少混亂，我更新了我的答案使用@Lafis增強，不使用包裝類應用擴展行爲。 upvoting時也請稱讚@Lafis。

Answer 2

要增強@martinoss答案，您可能會達到相同的結果，而不實施包裝。只需複製原始處理程序，指定一個實現重定向邏輯的新處理程序以修改context.RedirectionUri，並在最後調用原始處理程序。

CookieAuthenticationProvider provider = new CookieAuthenticationProvider(); 

var originalHandler = provider.OnApplyRedirect; 
provider.OnApplyRedirect = context => 
{ 
    //insert your logic here to generate the redirection URI 
    string NewURI = "...."; 
    //Overwrite the redirection uri 
    context.RedirectUri = NewURI; 
    originalHandler.Invoke(context); 
}; 

app.UseCookieAuthentication(new CookieAuthenticationOptions 
{ 
    AuthenticationType = DefaultAuthenticationTypes.ApplicationCookie, 
    LoginPath = new PathString(url.Action("Login", "Account")), 
    Provider = provider 
}); 

Answer 3

我發現了很多更簡單的方法：

UrlHelper _url = new UrlHelper(HttpContext.Current.Request.RequestContext); 

public void ConfigureAuth(IAppBuilder app) 
{ 
    String actionUri = _url.Action("Login", "Account", new { }); 
    String unescapeActionUri = System.Uri.UnescapeDataString(actionUri); 

    app.UseCookieAuthentication(new CookieAuthenticationOptions 
    { 
     AuthenticationType = DefaultAuthenticationTypes.ApplicationCookie, 
     LoginPath = new PathString(unescapeActionUri) 
    }); 

[...] 

Answer 4

如何：

var cao = new CookieAuthenticationOptions 
     { 
      AuthenticationType = DefaultAuthenticationTypes.ApplicationCookie, 
      LoginPath = new PathString("/Account/Login"), 
      Provider = new CookieAuthenticationProvider { OnApplyRedirect = ApplyRedirect } 
     }; 
app.UseCookieAuthentication(cao); 

和

private static void ApplyRedirect(CookieApplyRedirectContext context) 
    { 

     UrlHelper _url = new UrlHelper(HttpContext.Current.Request.RequestContext); 
     String actionUri = _url.Action("Login", "Account", new { }); 
     context.Response.Redirect(actionUri); 
    } 

Answer 5

我認爲我是一個今年年底在此答案，但這裏的主要目標是分享知識...... :)

我剛剛在我正在開發的應用程序中發現相同的問題。我研究了我們需要的代碼量（在之前的文章中）來解決這個問題，我很擔心（大部分代碼都很複雜，觸及了獸的內部）。所以，我試圖找到一個更簡單的解決方案，我所做的是以下路徑添加到我的路線集合：

routes.MapRoute(
      name: "loginRoute", 
      url: "account/login", 
      defaults:new { culture = "", controller = "account", action = "login", id = UrlParameter.Optional }); 

這將允許調用在帳戶控制我的登錄操作，我的標準機制（倍率時來自Controller的BeginExecuteCore方法）能夠將當前的UI文化附加到URL。

我希望它可以幫助別人。

補充：我的標準機制：

protected override IAsyncResult BeginExecuteCore(AsyncCallback callback, object state) 
    { 
     var cultureName = RouteData.Values["culture"] as string; 

     var cultureCookie = Request.Cookies["_culture"]; 
     if (cultureCookie != null && string.IsNullOrEmpty(cultureName)) 
     { 
      cultureName = cultureCookie.Value; 
     } 

     if (cultureName == null) 
      cultureName = Request.UserLanguages != null && Request.UserLanguages.Length > 0 ? Request.UserLanguages[0] : null; 

     cultureName = CultureHelper.GetImplementedCulture(cultureName); 

     if (RouteData.Values["culture"] as string != cultureName) 
     { 
      RouteData.Values["culture"] = cultureName.ToLowerInvariant(); // lower case too 

      var cookie = Request.Cookies["_culture"]; 
      if (cookie != null) 
       cookie.Value = cultureName; // update cookie value 
      else 
      { 
       cookie = new HttpCookie("_culture") { Value = cultureName, Expires = DateTime.Now.AddYears(1) }; 
      } 
      Response.Cookies.Add(cookie); 

      // Redirect user 
      Response.RedirectToRoute(RouteData.Values); 
     } 

     Thread.CurrentThread.CurrentCulture = new System.Globalization.CultureInfo(cultureName); 
     Thread.CurrentThread.CurrentUICulture = Thread.CurrentThread.CurrentCulture; 

     return base.BeginExecuteCore(callback, state); 
    } 

Answer 6

不佔用過多的URL格式等的責任，你可以這樣做以下

public static void Configuration(IAppBuilder app) 
{ 
    UrlHelper url = new UrlHelper(HttpContext.Current.Request.RequestContext); 
    app.UseCookieAuthentication(new CookieAuthenticationOptions 
    { 
     AuthenticationType = DefaultAuthenticationTypes.ApplicationCookie, 
     LoginPath = new PathString(url.Action("LogOn", "Account", new { area = "Account" })), 
     Provider = new CookieAuthenticationProvider 
     { 
      OnApplyRedirect = context => context.Response.Redirect(context.RedirectUri.Replace(CultureHelper.GetDefaultCulture(), Thread.CurrentUiCulture.Name)) 
     } 
    }); 
} 

Answer 7

我提高哨兵回答，保持返回網址：

private static void ApplyRedirect(CookieApplyRedirectContext context) 
     { 
      //use this way to keep return url 
      var loginUrl = context.RedirectUri.Insert(
       context.RedirectUri.IndexOf("/Account/Login"), 
       "/" + CultureHelper.GetCurrentCulture()); 

      context.Response.Redirect(loginUrl); 
     }