mime.types.conf int lighttpd

Elan Ruusamäe glen at pld-linux.org
Mon Feb 27 14:40:53 CET 2012

On 27.02.2012 15:02, Jacek Konieczny wrote:
 > 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 
 >> 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.
yes exactly,

and to satisfy both worlds, i propose to add new env var, that can be 
left empty by default and interested ones can set value which is 
appeneded text/* mime types.

mimetype_charsetheader = "; charset=\"utf-8\""

instead of current:

mimetype_textcharset = "utf-8"

and mime.types would contain:

     ".wmls"        => "text/vnd.wap.wmlscript" + mimetype_textcharset,

instead of
     ".wmls"        => "text/vnd.wap.wmlscript; charset=" + 


More information about the pld-devel-en mailing list