mime.types.conf int lighttpd

[Jacek Konieczny]

On Thu, Feb 16, 2012 at 08:45:39AM +0100, Paweł Gołaszewski wrote:
> There is added header:
> # charset used for "text/*" mimetypes
> mimetype_textcharset = "utf-8"
> 
> ...and some "charset= + mimetype_textcharset" entries.
> 
> It causes problems because encoding is not detected in pages, always utf-8 
> is used, no matter what header in html is set.

And that is exactly how that is supposed to work (but probably not what
the change author wanted).

Charset defined in the Content-Type HTTP header takes precedence over
anything else, especially the <meta/> tag in the HTML.

In the ideal world <meta/> would never be used for this purpose and
'charset' in Content-Type should be set, but in the real world many rely
on the <meta/> tag and forcing charset into the Content-Type header only
breaks things.

Greets,
        Jacek