Re: [tlug] Firefox 3.0.1 doesn't respect <meta http-equiv="content-type">

["Stephen J. Turnbull" <stephen@example.com>]

Curt Sampson writes:

 > What was the content-type from the meta tag, and what was the
 > content-type header served by the web server?

The content type in the meta tag is "text/html;charset=iso-2022-jp",
but curl -I sez:

steve@example.com ~ $ curl -I http://turnbull/mada.html
HTTP/1.1 200 OK
Date: Tue, 09 Sep 2008 06:32:41 GMT
Server: Apache/2.2.3 (Debian) DAV/2 mod_fastcgi/2.4.2 proxy_html/2.5 mod_ssl/2.2.3 OpenSSL/0.9.8e
Last-Modified: Tue, 13 Apr 2004 15:07:47 GMT
ETag: "318-e8-3982d6c0"
Accept-Ranges: bytes
Content-Length: 232
Content-Type: text/html; charset=UTF-8

I don't understand this last, since I don't have an active
AddDefaultCharset directive ... or do I, just had a horrible thought
[adds -r to the grep command] ... oh fsck, it's hidden in an include
file which is itself hidden in a subdirectory.

OK, I've changed the AddDefaultCharset directive to "off", and now it
works as expected (of course, I had to restart Firefox to get it to
forget about the old HTTP headers).  We'll see what happens with other
pages....

I observe ruefully that the concept of a default charset is pretty
broken given the priority of the server headers, the meta tag, and
browser guesstimates.  Oh well.