On Tuesday 18 March 2003 05:25, Pier Fumagalli wrote: > If, for example, in my corporation there are two guys, one using Windows in > jp and one using Linux in en_US, if the first guy requests > "http://www.vnunet.com/";, I'll deliver the page the first time in jp, > encoded in shift_jis (let's not track content-type for a sec). > > Now, when the second guy requests the same page, I'd have to send it in > en_US maybe encoded in iso-8859-1... > > But my corporation proxy (or the cocoon cache), will cache the first > version it hits, so, to both of them, I'll end up serving the same Japanese > shift_jis content...
That's why almost noone uses the Accept headers to determine the served language or encoding, but use different URL spaces. HTTP's biggest mess-up IMHO. To make matters worse, many ISPs (at least in Asia) has transparent caches that doesn't handle the Expires headers very well either, and you content becomes static for (among Malaysian ISPs) 24 hours. Niclas
