- From: Julian Reschke <julian.reschke@gmx.de>
- Date: Fri, 20 Mar 2009 14:15:05 +0100
Alexey Proskuryakov wrote: > > 20.03.2009, ? 1:43, Anne van Kesteren ???????(?): > >> Can we get away with not following Content-Type at all? As we do for >> text/event-stream and text/cache-manifest. Both which simply require >> UTF-8. > > > Good point - but to the contrary, I think that charset from Content-Type > should be always honored, adding special cases is an unnecessary > complication. Yep. > Formally, a proxy can re-encode any text/* resource and expect the > client to honor Content-Type charset over <meta> and built-in > preconceptions, although I think that such proxies are extremely rare in > this millennium. An easy way to avoid this issue is not to use a text/* content type. BR, Julian
Received on Friday, 20 March 2009 06:15:05 UTC