Bug #1015
closedlighthttpd + phpBB + utf-8
Description
Hello, I do have a problem, I can't set an default encoding on my website: http://ablforum.sniegas.lt I use phpBB from www.phpBB.de. How could I do this with lighthttpd? defaultcharset doesn't work ... :) I do have a problem in HTML too. http://info.sniegas.lt (some letters are showing wrong, some good)
maybe some of you have any ideas? It would be great!
cheers
-- SNow
Updated by jan about 18 years ago
- Status changed from New to Fixed
- Resolution set to invalid
Please check the forum for setup problems.
For static content you can use:
mimetype.assign = (
...,
".html" => "text/html; charset=utf-8",
...)
for content generated by PHP, check the php options.
Updated by dhill over 15 years ago
- Status changed from Invalid to Reopened
This seems similar enough to my problem. I'm trying to set default encoding for text files and alike, however in Ubuntu/Debian this data is generated by a Perl script from /etc/mime.types. Is there any configuration variable to set default encoding for all text data? I searched the net, but I couldn't find anything like it.
Updated by stbuehler over 15 years ago
- Status changed from Reopened to Invalid
- Missing in 1.5.x set to No
I don't think there is anything new to say. (It is your problem if you use the debian way of setting the mime type).
Updated by dhill over 15 years ago
So there is no way to set default encoding? I argue that it is very useful, most systems would have the same encoding across all files, no matter what mime type. I can override the content of mimetype.assign on the particular types I use and it has nothing to do with Debian, but that's not a solution, that's a workaround.
Why is ISO-8859-1 the default encoding then? What's the rationale behind it? It would be a different case (closer to what you argue), if the configuration variable required binary or charset/encoding-name parameter, then it would be Debian's problem, if they provided faulty defaults. They actually spared people a lot of tinkering by doing this automatically.
I won't be changing the status, I see it got you irritated, but nevertheless I expect an answer. I think there should at least be an explanation in the docs, if that's how it is to stay.
Updated by stbuehler over 15 years ago
You just don't understand how it works. The mime-types option is for setting the header "Content-Type" which may include the encoding. There is no reason for an extra option, as you already can specify it. And no, using an option is not a workaround!
And no, ISO-8859-1 is not the "default encoding", at least not on our side. It may be the default encoding of the browser, and there is nothing we can do about that.
And for php pages it is the job of your application to set the header.
And you could have found out that by just reading the first comment.
Updated by dhill over 15 years ago
I realized that it's the browser side just after leaving the computer... I know HTTP that much, I mean a little :).
I shouldn't have attached this comment to this bug. My situation is a bit different as I'm just serving text files. I have no way of sending HTTP headers. I would expect lighttpd to know my locale and act accordingly, just plain file serving. Maybe you're right and it could get in the way of somebody else. I'll just override the text/plain and be done with it.
Thanks for great software anyway.
Also available in: Atom