Open nmg196 opened 4 years ago
Did you try to use the QueryStringRequestCultureProvider like that: http://localhost:5000/?culture=es-MX&ui-culture=es-MX
?
That might help you understand where the problem is.
For example, I had a cookie (prevailing on header but not query string) I didn't know it was here but I realised because the url actually worked.
Hi, I've just ported a .NET Framework project to Core 3.1 and everything seems OK except that WW Globalization is alreadys returning the English resources.
Do I have to add some code or configuration to make it honour the Accept-Langage header?
Thanks