For a personal project I'm working on, I needed some way to set the HTTP 'Content-Language' header on responses, and toyed with a very simple middleware which would set the header based on the project's LANGUAGE_CODE setting before remembering LocaleMiddleware and thinking it ought to be able to do that. But a cursory examination of the code seems to indicate that LocaleMiddleware does not, in fact, send the 'Content-Language' header.
Since there are definitely use cases where this header is necessary (my current project is one such), and cases where it would likely be helpful (e.g., when multiple languages are listed in the request's 'Accept-Language' header it would probably be nice to include a Content-Language for the response which indicates the language Django chose to use), would this be a welcome addition to LocaleMiddleware? -- "May the forces of evil become confused on the way to your house." -- George Carlin --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django I18N" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/Django-I18N -~----------~----~----~----~------~----~------~--~---
