Bug#397886: apache2.2-common: non wanted behaviour during upgrade: charset MUST not be created without user consent
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. The problem is,
of course, that it's difficult for apache2.2-common to see that it was
"upgraded" from apache2-common.
/* Steinar */
--
Homepage: http://www.sesse.net/
Reply to: