Re: +n- Flaw in IE

Java script Dude wrote:

> I agree, if the server is serving the file up with the encoding in the
> http header properly, this will not be a problem. But as I have tested
> and confirmed, IE ignores the http-equiv meta tag and when in pure
> 'Auto-Detect' mode and tries to figure itself which mode by reading
> content. [...]
> IE must not ignore the http-equiv meta tags. [...]

True, in _this_ case.[1]
 
HTTP/1.1 (RFC2616[2]) section 3.4.1 specifies that it MUST ignore them
if the server already sent a Content-Type header with a `charset' label.

[1]
<URL:http://www.w3.org/TR/1999/REC-html401-19991224/charset.html#h-5.2.2>
[2] <URL:http://www.rfc-editor.org/rfc/rfc2616.txt>
 
> Moral of the story - Use UTF-8 encoding and hard encode static content
> and explicitly specify content encoding in http headers.

No, moral of the story is to serve all text resources with
Content-Type header and `charset' label always, and remove
unconditional AddDefaultCharset directives from httpd.conf.

PointedEars
Received on Tue Jan 17 17:13:23 2006