In a digital archaeology project I have found a web server directory with files dated from 2001 that had a peculiar collection of index.html files with names ending with two letter codes of different languages and language charsets, i.e.index.html.ca       index.html.ja.jis   index.html.ru.iso-ruindex.html.cz       index.html.kr.iso-kr    index.html.ru.koi8-rindex.html.de       index.html.lb.utf8  index.html.ru.ucs2index.html.dk       index.html.nl       index.html.ru.ucs4index.html.ee       index.html.nn       index.html.ru.utf8...How do I configure modern Apache to serve different static pages based on the value of Accept-Language header?
Serve index.html by language and charset (a thing from the past)
apache;internationalization;language
Those files are almost certainly meant to be served via Apache content negotiation. Since there does not appear to be a .var file to serve as an explicit type map, and since the file name extensions correspond to standard language and charset codes, they're probably meant to be used with the implicit MultiViews mechanism.To enable MultiViews for the directory containing these files, add the following directive into an .htaccess file in that directory (or into a matching <Directory> section in the global Apache config):Options +MultiViewsThis will make Apache automatically resolve requests for nonexistent files by appending additional extensions based on the language, MIME type and charset preferences indicated by the HTTP Accept, Accept-Charset and Accept-Language headers. For example, a request for index.html might cause Apache to instead return the contents of  index.html.de or index.html.ja.jis or index.html.ru.utf8, depending on the preferred language(s) configured in the user's browser.Note that, in addition to content negotiation, you should also provide some way for users to explicitly select the version of the page that they prefer. When using MultiViews, this can be as simple as providing direct links to the translated pages with the language code included.