Accept-Language request HTTP header advertises which languages the client is able to understand, and which locale variant is preferred. Using content negotiation, the server then selects one of the proposals, uses it and informs the client of its choice with the
Content-Language response header. Browsers set adequate values for this header according their user interface language and even if a user can change it, this happens rarely (and is frown upon as it leads to fingerprinting).
This header is a hint to be used when the server has no way of determining the language via another way, like a specific URL, that is controlled by an explicit user decision. It is recommended that the server never overrides an explicit decision. The content of the
Accept-Language is often out of the control of the user (like when traveling and using an Internet Cafe in a different country); the user may also want to visit a page in another language than the locale of their user interface.
If the server cannot serve any matching language, it can theoretically send back a
406 (Not Acceptable) error code. But, for a better user experience, this is rarely done and more common way is to ignore the
Accept-Language header in this case.
|Header type||Request header|
|Forbidden header name||no|
Accept-Language: <language> Accept-Language: <locale> Accept-Language: * // Multiple types, weighted with the quality value syntax: Accept-Language: fr-CH, fr;q=0.9, en;q=0.8, de;q=0.7, *;q=0.5
- 语言码，包含 2 个或者 3 个字符
- 完整的语言标签。In addition to the language itself, it may contains additional information after a
'-'. The most common extra information is the country variant (like
'en-US') or the type of alphabet to use (like
'sr-Lat'). Other variants like the type of orthography (
'de-DE-1996') are usually not used in the context of this header.
- Any language;
'*'is used as a wildcard.
- Any value placed in an order of preference expressed using a relative quality value called weight.
Accept-Language: de Accept-Language: de-CH Accept-Language: en-US,en;q=0.5
|RFC 7231, section 5.3.5: Accept-Language||Hypertext Transfer Protocol (HTTP/1.1): Semantics and Context|
The compatibility table in this page is generated from structured data. If you'd like to contribute to the data, please check out https://github.com/mdn/browser-compat-data and send us a pull request.
|Feature||Android||Chrome for Android||Edge Mobile||Firefox for Android||IE Mobile||Opera Mobile||Safari Mobile|