W3C home > Mailing lists > Public > whatwg@whatwg.org > March 2009

[whatwg] Text Encoding used to decode appcache manifest

From: Julian Reschke <julian.reschke@gmx.de>
Date: Fri, 20 Mar 2009 14:15:05 +0100
Message-ID: <49C396D9.6050009@gmx.de>
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 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Wednesday, 30 January 2013 18:47:49 GMT