ASP.NET Core Request Localization Options

Question

Here is my custom request culture provider which returns "en" as a default culture if no culture specified in url (for example http://example.com/ru or http://example.com/en). My idea to show website on that language which is default in user's browser, so I'm looking a way how to determine it and return it instead of: return Task.FromResult(new ProviderCultureResult("en", "en"));

services.Configure<RequestLocalizationOptions>(options =>
{
    var supportedCultures = new List<CultureInfo>
    {
        new CultureInfo("en"),
        new CultureInfo("ru")                            
    };

    options.DefaultRequestCulture = new RequestCulture(culture: "en", uiCulture: "en");
    options.SupportedCultures = supportedCultures;
    options.SupportedUICultures = supportedCultures;
            
    options.RequestCultureProviders.Insert(0, new CustomRequestCultureProvider(context =>
    {                    
        var pathSegments = context.Request.Path.Value.Split('/');
        if (pathSegments.Count() > 0)
        if (supportedCultures.Select(x => x.TwoLetterISOLanguageName).Contains((pathSegments[1])))
            return Task.FromResult(new ProviderCultureResult(pathSegments[1], pathSegments[1]));
       return Task.FromResult(new ProviderCultureResult("en", "en"));
   }));
});

adem caglin · Accepted Answer · 2016-08-18 06:54:28Z

45

You can get Accept-Language header from the current Request and set default language. Your code should be something like this:

services.Configure<RequestLocalizationOptions>(options =>
{
    //...

    options.RequestCultureProviders.Insert(0, new CustomRequestCultureProvider(context =>
    {                    
       //...
       var userLangs = context.Request.Headers["Accept-Language"].ToString();
       var firstLang = userLangs.Split(',').FirstOrDefault();
       var defaultLang = string.IsNullOrEmpty(firstLang) ? "en" : firstLang;
       return Task.FromResult(new ProviderCultureResult(defaultLang, defaultLang));
   }));
});

answered Aug 18, 2016 at 6:54

adem caglin

24.5k10 gold badges65 silver badges80 bronze badges

Sign up to request clarification or add additional context in comments.

1 Comment

Sergey Sypalo Over a year ago

Thanks a lot Adem, this is exactly what I was looking for!

Dennis de Laat · Accepted Answer · 2018-05-15 13:12:11Z

36

Another way to get the Accept-Language header with a framework call (ASP.NET Core):

HttpContext.Request.GetTypedHeaders().AcceptLanguage

answered May 15, 2018 at 13:12

Dennis de Laat

5431 gold badge5 silver badges10 bronze badges

1 Comment

Evgeni Nabokov Over a year ago

Do not forget to order languages by its priority q, e.g. OrderByDescending(x => x.Quality ?? 1).

Nick Kovalsky · Accepted Answer · 2020-08-12 15:28:28Z

Inside your public class Startup:

public void Configure(IApplicationBuilder app, IHostingEnvironment env)
{
    //...

    app.Use((context, next) =>
    {
        //get client prefered language
        var userLangs = context.Request.Headers["Accept-Language"].ToString();
        var firstLang = userLangs.Split(',').FirstOrDefault();

        //set allowed alanguage
        var lang = "en"; //default
        switch (firstLang)
        {
            case "hy": //allowed
            case "ru": //allowed
                lang = firstLang; 
                break;
            default:
                //client language not supported
                lang = "en"; //use our default
                break;
        }

        //switch culture
        Thread.CurrentThread.CurrentCulture = new System.Globalization.CultureInfo(lang);
        Thread.CurrentThread.CurrentUICulture = Thread.CurrentThread.CurrentCulture;

        //save for later use
        context.Items["ClientLang"] = lang;
        context.Items["ClientCulture"] = Thread.CurrentThread.CurrentUICulture.Name;
        
        // Call the next delegate/middleware in the pipeline
        return next();
    });

    //... then goes app.UseMvc etc..

}

Dongdong · Accepted Answer · 2018-12-02 15:49:26Z

4

as an additional option, Here is a full solution: Handle culture in route (URL) via RequestCultureProviders

as an option as well, here is a simplified code for CustomRequestCultureProvider:

options.RequestCultureProviders.Insert(0, new CustomRequestCultureProvider(context =>
{
    var lang = context.Request.GetTypedHeaders().AcceptLanguage.FirstOrDefault()?.Value.Value ?? Constants.Languages.EN_US;

    return Task.FromResult(new ProviderCultureResult(lang, lang));

}));

answered Dec 2, 2018 at 15:49

Dongdong

2,53824 silver badges34 bronze badges

Collectives™ on Stack Overflow

ASP.NET Core Request Localization Options

4 Answers 4

1 Comment

1 Comment

Comments

Comments

Your Answer

Linked

Hot Network Questions

Collectives™ on Stack Overflow

4 Answers 4

1 Comment

1 Comment

Comments

Comments

Your Answer

Sign up or log in

Post as a guest

Linked

Related