I believe browsers typically try to guess. If Apache serves a page that doesn't have any non-ASCII characters in it, then browsers can guess, and "windows-1252" would still be correct, since the document was a strict subset of this charset.
What happens if you serve a UTF-8 encoded file? What does the browser do then? If you want Apache to assume that everything in /var/www is UTF-8 by default, and explicitly set that in every response, then I can understand such a request, but I think it needs to be coordinated with the Debian packaging, perhaps also including upstream's view on a suitable default. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to apache2 in Ubuntu. https://bugs.launchpad.net/bugs/1258546 Title: Apache2 defaults to the wrong character set, it should be UTF-8 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apache2/+bug/1258546/+subscriptions -- Ubuntu-server-bugs mailing list [email protected] Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
