Page History

...

The first represents language expressed as a 2 or 3-character string, the second represents language as a full language tag, the third says "any language" (see Accept-Language and Language Tags in RFC-2616).

Additionally, the language defined – locale value that is sent in the header – optionally in a semicolon-delimited range for more languages – may be given an associated quality value ( q=<qvalue> ) which . The quality value represents an estimate of the user's preference for the languages specified by that range, for example:

...

A site in Magnolia may be configured to look set reflect the site's locale according to the information provided in this the Accept-Language header, see the configuration section below.

...

The preferred locale information may be sent to the server as a part of a Request-URI . See below in the configuration section how to configure a site in Magnolia to parse Request-URI for locale information, such , such as de in the following example:

/de/tour-type~active~.html

See the section below how to configure a site in Magnolia to parse Request-URI for locale preference.

Configuring site locale