Package: apache2 Version: 2.2.3-3.3 Severity: serious Justification: Causes unexpected changes in behavior of websites After upgrading my (home) server from Sarge to Etch I noticed that the word "Privé" on one of my webpages was not served correctly anymore. The default encoding of the system itself was not changed during the upgrade, but apparently the default encoding set by apache2 in absence of an encoding in the html headers has. After discussion with Peter Samuelson (and others) on #d-devel, we suspect this new config file to be the culprit: $ cat /etc/apache2/conf.d/charset AddDefaultCharset UTF-8 Apparently that file was not supposed to be created on upgrades, but is. Not entirely sure that this is RC, but the consensus on IRC was that this is quite a nasty unexpected behavior change that can be hard to spot during regular post-upgrade checks (and downgrading is easy). -- System Information: Debian Release: 4.0 APT prefers testing APT policy: (500, 'testing') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.18-4-686 Locale: LANG=en_US, LC_CTYPE=en_US (charmap=ISO-8859-1) Versions of packages apache2 depends on: ii apache2-mpm-worker 2.2.3-3.3 High speed threaded model for Apac apache2 recommends no packages. -- no debconf information
Attachment:
pgpVHjrTAPoPY.pgp
Description: PGP signature