DefaultRequestCulture not working when change to non-en culture in 3.1.3 about expresslocalization HOT 3 CLOSED

Great, it working now. Hope you can add this to your documentation. Thanks!

from expresslocalization.

First I will give the solution, then you can read the explanation for more details.

Disable the framework localization culture providers and use only RouteSegmentCultureProvider as below:

services.AddRazorPages()
            .AddExpressLocalization<ExpressLocalizationResource, ViewLocalizationResource>(ops =>
            {
                // Use only route segment culture provider
                 ops.UseAllCultureProviders = false;
               
                // the rest of the code...
             });

Explanation

When using all the localization culture providers, the localization process will check all available culture providers in order to detect the request culture. If the request culture is found it will stop checking and do localization accordingly. If the request culture is not found it will check the next provider by order. Finally if no culture is detected the default culture will be used.

Checking order for request culture:

1. RouteSegmentCultureProvider
2. QueryStringRequestCultureProvider
3. CookieRequestCultureProvider
4. AcceptedLanguageHeaderRequestCultureProvider
5. Use default request culture from startup settings

So, in your case, I can guess that the localization is falling to no. 4, you can check it in your browser settings.

If you don't prefere this behavior, you can simply use only RouteSegmentCultureProvider and disable other providers as mentioned above, so when there is no culture in the route the default culture will be used.

from expresslocalization.

Thanks for your feedback, I'll add it to the docs soon :)

from expresslocalization.