Bug#397886: apache2.2-common: non wanted behaviour during upgrade: charset MUST not be created without user consent
Steinar H. Gunderson a écrit :
> On Fri, Dec 22, 2006 at 06:42:46PM +0100, Daniel Déchelotte wrote:
> > But setting such a DefaultCharset *breaks* *working* pages (and
> > perfectly valid ones) for very little benefit. Sites that use latin
> > encoding for latin characters are *not* broken.
>
> Discussions about best behavior aside, just to summarize: The bug
> here (if any) is that AddDefaultCharset is added even on an upgrade.
> [...]
This might have been discussed somewhere before, but why set a
default charset at the first place (even for fresh installs)? I agree
that it may help for files that do not explicitely specify their
encodings, i.e., plain text files. Provided that they are indeed UTF-8
files. But are there any others cases where it is needed? Would there
be a way to limite the scope of the default charset to the only files
whose mime type is text/plain? Anyways, the server doesn't have to force
an "arbitrary" charset when it is not specified: apache can let it
unspecified, and up to the client to guess.
For every other mime types (html, static or not, xml, ...), the "blind"
HTTP directive is to supercede the correct indication contained in the
file, and break it.
A similar (albeit old) bug against apache is #305495.
--
Daniel Déchelotte
http://yo.dan.free.fr/
Reply to: