The Content-Language
entity header is used to describe the language(s) intended for the audience, so that it allows a user to differentiate according to the users' own preferred language.
For example, if "Content-Language: de-DE
" is set, it says that the document is intended for German language speakers (however, it doesn't indicate the document is written in German. For example, it might be written in English as part of a language course for German speakers).
If no Content-Language
is specified, the default is that the content is intended for all language audiences. Multiple language tags are also possible, as well as applying the Content-Language
header to various media types and not only to textual documents.
Header type | {{Glossary("Entity header")}} |
---|---|
{{Glossary("Forbidden header name")}} | no |
Syntax
Content-Language: de-DE Content-Language: en-US Content-Language: de-DE, en-CA
Directives
language-tag
- Multiple language tags are separated by comma. Each language tag is a sequence of one or more case-insensitive subtags, each separated by a hyphen character ("-", %x2D). In most cases, a language tag consists of a primary language subtag that identifies a broad family of related languages (e.g., "en" = English), which is optionally followed by a series of subtags that refine or narrow that language's range (e.g., "en-CA" = the variety of English as communicated in Canada).
Specifications
Specification | Title |
---|---|
{{RFC("7231", "Content-Language", "3.1.3.2")}} | Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content |
Browser compatibility
To contribute to this compatibility data, please write a pull request against this file: https://github.com/mdn/browser-compat-data/blob/master/http/headers.json.
{{Compat}}
See also
- {{HTTPHeader("Accept-Language")}}