First, you should check out this msdn discussion.
For a better approach to this problem. You must set the globalization setting in the web.config file.
<configuration> <system.web> <globalization enableClientBasedCulture="true|false" requestEncoding="any valid encoding string" responseEncoding="any valid encoding string" fileEncoding="any valid encoding string" responseHeaderEncoding = "any valid encoding string" resourceProviderFactoryType = string enableBestFitResponseEncoding = "true|false" culture="any valid culture string" uiCulture="any valid culture string"/>
For the case of English culture
<globalization enableClientBasedCulture="false" uiCulture="en-US" culture="en-US" />
With this, you can use the culture stream with configuration. You can also set culturethread with browser settings to auto, you can be set to automatic and ignore some cases. For more information, you can check the link above.
If you want to embrace browser culture
<globalization enableClientBasedCulture="true" uiCulture="auto" culture="auto" />
Or with a default action
<globalization enableClientBasedCulture="true" uiCulture="auto:en-US" culture="auto:en-US" />
For best practice, you never change the culture information of a computer stream. But you can change the current culture of a session-based thread, this is just thread-based information, not the whole system. Hope this will be helpful.
source share