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).
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||Entity header|
|Forbidden header name||no|
Content-Language: de-DE Content-Language: en-US Content-Language: de-DE, en-CA
%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).
Do not use this meta element like this for stating a document language:
<!-- /!\ This is bad practice --> <meta http-equiv="content-language" content="de">
Content-Language header is used to specify the intended audience of the page, and can indicate that this is more than one language.
Content-Language: de, en
|RFC 7231, section 184.108.40.206: Content-Language||Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content|
|Android webview||Chrome for Android||Edge Mobile||Firefox for Android||Opera for Android||iOS Safari||Samsung Internet|
© 2005–2018 Mozilla Developer Network and individual contributors.
Licensed under the Creative Commons Attribution-ShareAlike License v2.5 or later.