On 25/02/12 23:35, Paweł Gołaszewski wrote:
On Sat, 25 Feb 2012, g...@pld-linux.org wrote:
There is problem with recent change in lighttpd-mime.types.sh (it
generates mime.types.conf).
[...]
revision 1.3
date: 2012/01/22 20:52:51; author: glen; state: Exp; lines: +15 -1;
kopt: kv; commitid: 64d94f1c7723ee01; filename: lighttpd-mime.types.sh;
- add charset to text content-types; default as utf8
[...]
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.
Tested on AC.
This should be reversed...
perhaps then mimetype_charsetheader = "; charset=\"utf-8\""
to be able to leave it empty meaning no charset is enforced
Any docs about that option? I can't find anything about that...
Any encoding set in user files CAN'T be overwriten...
P.S.: I wanted revert your changes today...
docs of what? mimetype.assign = ()?
there are no docs, in pld mimetype.assign is generated from
/etc/mime.types, and the charset header is just programmed using string
concat that lighttpd config engine supports.
so, that go with that last option (mimetype_charsetheader = ";
charset=\"utf-8\"") ?, better than completely reverting...
and you seem to mean by "user files" html <meta http equiv>?
http://redmine.lighttpd.net/projects/lighttpd/wiki/Docs:Configuration
http://redmine.lighttpd.net/projects/lighttpd/wiki/Mimetype.assignDetails
--
glen
_______________________________________________
pld-devel-en mailing list
pld-devel-en@lists.pld-linux.org
http://lists.pld-linux.org/mailman/listinfo/pld-devel-en
