Yep. That was why I suggested accessing the web page directly rather than change the settings. Which state are U in now? Tim wrote: >If you used a URI ending .html.de (like the above), you will get that >page directly, bypassing any language negotiation that the server might >have offered. Alternatively, if the URI was shortened to not include >the country, e.g. <http://www2.uibk.ac.at/fakultaeten/index.html>, then >the server is free to negotiate which language variant it serves you, if >they exist. > >e.g. It might have index.html.de index.html.en index.html.fr > >And you'd get the best match served to you *as* "index.html". > >This might be where de-de was falling down - the server looking for >something specific, with no obviously equivalent alternative (to it). > >Different servers have different negotiation abilities, too. My site >suffers because the host still uses Apache 1.3.x. Anybody visiting >without their browser configured to accept English, amongst any other >languages, gets a 406 error, rather than my English pages anyway. >Apache 2 can avoid that annoying problem, by letting the webmaster >configure a fallback. > >(I use content negotiation for a different purpose than language >negotiation.) >
