Yes, the headers are the same on both, there is no header directive to set character set, as I have stated.
IE, there is nothing like <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1" /> in the header.
There has to be something different in the 2 apache servers, the one that works is an older 2.4.4 and the new one is 2.4.57 that is not working right.
Still can’t figure out what is causing the difference.
From: Frank Gingras <thumbs@xxxxxxxxxx>
Sent: Saturday, November 11, 2023 5:44 PM
To: users@xxxxxxxxxxxxxxxx
Subject: Re: [users@httpd] Unicode Chars not working
Seeing how it's an exact copy from the other server and the other server is fine I would think that's more of a Apache configuration isn't it?
The content itself does not specify a character set.
-------- Original message --------
Date: 2023-11-11 4:02 p.m. (GMT-08:00)
Subject: Re: [users@httpd] Unicode Chars not working
Hi,
I am moving my site from one server to another, both are apache 2. The files where tarred and zipped on one linux server and copied to another linux server.
On the new server, any pages with a Unicode character is getting served with the black diamond and question mark.
I enabled AddDefaultCharset UTF-8 on the new server it does not make a difference.
What else do I need to change?
Are you sure your content is not producing html header with the wrong charset? I would inspect it.
Try to inspect the response headers with your browser (F12) next.
