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

[whatwg] Text Encoding used to decode appcache manifest

From: Alexey Proskuryakov <ap@webkit.org>
Date: Fri, 20 Mar 2009 12:19:32 +0300
Message-ID: <58027DB5-C82C-4EEE-B40C-3D8A765E1ABA@webkit.org>

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  

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.

- WBR, Alexey Proskuryakov
Received on Friday, 20 March 2009 02:19:32 UTC

This archive was generated by hypermail 2.3.1 : Monday, 13 April 2015 23:08:48 UTC