• Introducing WebPros Cloud - a fully managed infrastructure platform purpose-built to simplify the deployment of WebPros products !  WebPros Cloud enables you to easily deliver WebPros solutions — without the complexity of managing the infrastructure.
    Join the pilot program today!
  • Support for BIND DNS has been removed from Plesk for Windows due to security and maintenance risks.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS.

page encoding wrong

P

perler

Guest
hi,

this is not really plesk related but maybe someone had the problem and knows a solution:

i moved domains from a debian 3.1 server to a debian 4.0 server and migrated from plesk 7.5 to 8.2(.1 later)

i realized, that the apache2 on the new box had a file

/etc/apache2/conf.d/charset

with

AddDefaultCharset UTF-8

in it, which overwrites the default encoding served by apache, which is ISO-8859-1. this broke some of the sites i serve, so i commented this out to have the same configuration like on the old server.

now the strange thing:

this site: http://unsersteuerberater.de worked on the old server, (see here: http://patsplanet.com/us/) it is UTF-8 encoded and the meta statement did overwrite the encoding statement in the header served by apache2.

but on the new server, with the same settings and even with

AddDefaultCharset off

the server declares in the header, this is ISO-8859-1 and all browsers ignore the meta statement which declares this document is encoded in UTF-8 (for instance if you right click in firefox and then "View Page Info")

any idea why this is?

PAT
 
ok, problem solved, it was a default_charset=8859-1 statement in php.ini which took precedence over the meta tag

PAT
 
Back
Top