I figure this is an apache issue, but I dont' know where to look. Since moving my website from an older Redhat installation to my new Centos 4 server (all updates installed), all my web pages display a "?" anywhere I have a non-breaking space. If I do a view source in my browser I see the " " character, but when looking at it on my server via ssh, I see a vertical bar, similar, but not a pipe. And when looking at the source on a different browser I see a ASCII 160 character. But on all browsers, I'm seeing a ? on the display, instead of the non-breaking space.
Anyone know what I need to configure/correct/change in Apache to correct this?
Thanks, Scott
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On Thu, Dec 08, 2005 at 09:19:26PM -0600, scott wrote:
I figure this is an apache issue, but I dont' know where to look. Since moving my website from an older Redhat installation to my new Centos 4 server (all updates installed), all my web pages display a "?" anywhere I have a non-breaking space. If I do a view source in my browser I see the " " character, but when looking at it on my server via ssh, I see a vertical bar, similar, but not a pipe. And when looking at the source on a different browser I see a ASCII 160 character. But on all browsers, I'm seeing a ? on the display, instead of the non-breaking space.
Anyone know what I need to configure/correct/change in Apache to correct this?
This surely seems a charset related problem to me.
Try using the "file" command to see your files are using a different codepage. CentOS 4 uses UTF-8 by default.
[]s
- -- Rodrigo Barbosa rodrigob@suespammers.org "Quid quid Latine dictum sit, altum viditur" "Be excellent to each other ..." - Bill & Ted (Wyld Stallyns)
scott wrote:
I figure this is an apache issue, but I dont' know where to look. Since moving my website from an older Redhat installation to my new Centos 4 server (all updates installed), all my web pages display a "?" anywhere I have a non-breaking space. If I do a view source in my browser I see the " " character, but when looking at it on my server via ssh, I see a vertical bar, similar, but not a pipe. And when looking at the source on a different browser I see a ASCII 160 character. But on all browsers, I'm seeing a ? on the display, instead of the non-breaking space.
Anyone know what I need to configure/correct/change in Apache to correct this?
We ran into this, too. Look in /etc/httpd/conf/httpd.conf and find the line that reads:
AddDefaultCharset UTF-8
Comment it out and add a line just below it that reads:
AddDefaultCharset iso-8859-1
Then restart or reload Apache. The problem is that the default configuration sets the default character set for all pages to UTF-8 instead of the 'real' default of iso-8859-1, AKA latin1. There's a nice little block of comments just above it that explains what it is all about.
Hope that helps!
Jay:
scott wrote:
I figure this is an apache issue, but I dont' know where to look. Since moving my website from an older Redhat installation to my new Centos 4 server (all updates installed), all my web pages display a "?" anywhere
I
have a non-breaking space. If I do a view source in my browser I see
the "
" character, but when looking at it on my server via ssh, I see a
vertical
bar, similar, but not a pipe. And when looking at the source on a
different
browser I see a ASCII 160 character. But on all browsers, I'm seeing a
? on
the display, instead of the non-breaking space.
Anyone know what I need to configure/correct/change in Apache to correct this?
We ran into this, too. Look in /etc/httpd/conf/httpd.conf and find the line that reads:
AddDefaultCharset UTF-8Comment it out and add a line just below it that reads:
AddDefaultCharset iso-8859-1Then restart or reload Apache. The problem is that the default configuration sets the default character set for all pages to UTF-8 instead of the 'real' default of iso-8859-1, AKA latin1. There's a nice little block of comments just above it that explains what it is all about.
Hope that helps!
This did the trick. Thanks VERY much Jay. I figured teh problem was related to that parameter, but just didnt' know what to do with it. My old .cof file had it the same way (UTF-8) but not the behavior. But in any case, this fixed it. MUCH appreciated.
Best, Scott
-
Jay Leafey -
Rodrigo Barbosa -
scott