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.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/60.0.3112.113 Safari/537.36

...

From the Accept-Language header

The Public instance delivers the final page to a page visitor, and tries to deliver it in a way that fulfills the content of the HTTP request for the page. A part of the HTTP request's header defines which languages the visitor (client) is able to understand, and which locale variant of the page is preferred. The part that does this is the Accept-Language request header and The Accept-Language request header of an HTTP request defines which languages variant of a requested page would by 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).

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

Configuring site locale