Page History

...

• identifies the language variant of the software sending the request rather than the software's user's preferred locale, 
• is usually redundant,

• and more often than not is missing:

  Code Block
  Mozilla/5.0 (Windows NT 10.0X11; Win64; x64Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/6063.0.31123239.11384 Safari/537.36

Magnolia has no direct means how to check for the existence of and retrieve this type of locale information. The preferred locale information is communicated via the Accept-Language header.

...

The Accept-Language request header of an HTTP request defines which languages language variant of a requested the page would by is preferred by the public user. This locale information may take one of the following three forms:

...

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).

In addition, each language-range may be given an associated quality value ( q=<qvalue> ) which represents an estimate of the user's preference for the languages specified by that range, for example:

Accept-Language: cs-CZ,cs;q=0.9,en-US;q=0.8,en;q=0.7

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

From Request-URI

The most common form of Request-URI is that used to identify a resource on an origin server or gateway. For example:

https://demopublic.magnolia-cms.com/tour-type~active~.html

Configuring site locale