.NET WebApi 2.0全局文化配置：如何实现用户切换文化功能

Got it, let's tackle how to add culture switching to your .NET Web API 2.0 project (non-Core) since you've got the default culture set to it-IT in web.config with enableClientBasedCulture="false". Here's a practical, step-by-step approach:

1. Create a Custom Culture Handler #

We'll use a DelegatingHandler to intercept incoming requests and set the culture based on user input (query string, request header, or cookie). This runs early in the request pipeline, ensuring all controller logic uses the correct culture.

public class CultureHandler : DelegatingHandler
{
    protected override async Task<HttpResponseMessage> SendAsync(HttpRequestMessage request, CancellationToken cancellationToken)
    {
        string cultureName = null;

        // Check query string first (e.g., ?culture=en-US)
        var cultureQuery = request.GetQueryNameValuePairs()
            .FirstOrDefault(q => string.Compare(q.Key, "culture", StringComparison.OrdinalIgnoreCase) == 0);
        if (!string.IsNullOrEmpty(cultureQuery.Value))
        {
            cultureName = cultureQuery.Value;
        }
        // Fallback to Accept-Language header
        else if (request.Headers.AcceptLanguage?.Any() == true)
        {
            cultureName = request.Headers.AcceptLanguage.First().Value;
        }
        // Fallback to user's saved cookie
        else
        {
            var cultureCookie = request.Headers.GetCookies("UserCulture").FirstOrDefault();
            if (cultureCookie?["UserCulture"] != null)
            {
                cultureName = cultureCookie["UserCulture"].Value;
            }
        }

        // Validate and apply the culture if valid
        if (!string.IsNullOrEmpty(cultureName) && 
            CultureInfo.GetCultures(CultureTypes.AllCultures)
                .Any(c => string.Equals(c.Name, cultureName, StringComparison.OrdinalIgnoreCase)))
        {
            var culture = new CultureInfo(cultureName);
            Thread.CurrentThread.CurrentCulture = culture;
            Thread.CurrentThread.CurrentUICulture = culture;
        }

        // Pass the request through to the next handler/controller
        var response = await base.SendAsync(request, cancellationToken);
        return response;
    }
}

2. Register the Handler in Web API Pipeline #

Add the handler to your WebApiConfig so it's applied to all incoming requests:

public static class WebApiConfig
{
    public static void Register(HttpConfiguration config)
    {
        // Add our custom culture handler first
        config.MessageHandlers.Add(new CultureHandler());

        // Your existing route configuration
        config.MapHttpAttributeRoutes();

        config.Routes.MapHttpRoute(
            name: "DefaultApi",
            routeTemplate: "api/{controller}/{id}",
            defaults: new { id = RouteParameter.Optional }
        );
    }
}

3. Add an API Endpoint to Save User's Culture Preference #

Create a controller to let users save their preferred culture to a cookie, so they don't have to specify it on every request:

public class CultureController : ApiController
{
    [HttpPost]
    public IHttpActionResult SetPreferredCulture(string culture)
    {
        // Validate the culture code
        if (!CultureInfo.GetCultures(CultureTypes.AllCultures)
            .Any(c => string.Equals(c.Name, culture, StringComparison.OrdinalIgnoreCase)))
        {
            return BadRequest("Invalid culture code. Please use a valid format like 'en-US' or 'it-IT'.");
        }

        // Create a persistent cookie (expires in 30 days)
        var cultureCookie = new CookieHeaderValue("UserCulture", culture)
        {
            Expires = DateTimeOffset.UtcNow.AddDays(30),
            Domain = Request.RequestUri.Host,
            Path = "/"
        };

        // Attach the cookie to the response
        var response = new HttpResponseMessage(HttpStatusCode.OK)
        {
            Content = new StringContent($"Successfully set culture to {culture}")
        };
        response.Headers.AddCookies(new[] { cultureCookie });
        return ResponseMessage(response);
    }
}

Key Notes #

• Keep your existing web.config globalization settings as-is (enableClientBasedCulture="false"). Our handler takes over culture detection, so we don't need the default client-based behavior.
• For temporary culture switches, users can just append ?culture=fr-FR to any API request.
• If you need to support culture fallback (e.g., en → en-US), replace new CultureInfo(cultureName) with CultureInfo.CreateSpecificCulture(cultureName).
• In async controller methods, make sure you're using ConfigureAwait(true) (the default in Web API) to preserve the culture context across async operations.

内容的提问来源于stack exchange，提问作者DarioN1