On 9/9/09 6:28 AM, Tisza Gergő wrote: > The LanguageSelector extension [1] can automatically set the interface > language based on browser settings, which is nowadays the norm for > every serious multilanguage web page. It is not used on WMF wikis, > because it would interfere with caching. The strategic planning wiki > [2] has, however, relatively low traffic, and probably much higher > logged-in to anon ratio than the rest of the sites. Any chance > LanguageSelector (or something equivalent, if it exists) could be used > there?
Not sure; it ties in with the rest of our infrastructure so it's got the same caching layers in front of it... We've been hashing around the idea of allowing Accept-Language through for eg Chinese variant selection, but the main problem with doing it well is that we need some pre-processing at the cache level to keep the cache locality relatively non-insane. :) The set of possible Accept-Language headers is open-ended and huge, so we can't just add a Vary: without greatly increasing the amount of cache space that'll be used by that site. That would be easier to do with Varnish (which has a much cleaner plug-in system) than with Squid, but we're nowhere near a Varnish deployment yet. Mark, how hard would it be in theory to swap some settings around to make one of our low-traffic sites take different caching characteristics, like leaving just strategy.wikimedia.org with either a Vary: Accept-Language or just having it not cache as much? -- brion _______________________________________________ Wikitech-l mailing list [email protected] https://lists.wikimedia.org/mailman/listinfo/wikitech-l
