[CentOS] RE: OT: Problems with Pound Signs and Apache

[Bisbal, Prentice]

Are you sure ALL the files are 100% the same, including executables and
libraries? I would do an md5sum of EVERY file that might be even
remotely related to the behavior of Apache, Horde and anything else and
then compare the MD5sums of all the files on the two different systems. 

If that doesn't turn up anything, then do rpm -qa and make sure all the
packages are at the same version. The problem can still be in a library
used by Horde or apache that's further down the stack (we all know what
problems changing libc can cause, don't we? ) 

 If THAT doesn't turn up anything, do rpm -Va to verify all the packages
on the two systems. 


-- 
Prentice 

-----Original Message-----
From: centos-bounces at centos.org [mailto:centos-bounces at centos.org] On
Behalf Of Andy Wright
Sent: Friday, October 20, 2006 9:44 AM
To: CentOS mailing list
Subject: Re: [CentOS] RE: OT: Problems with Pound Signs and Apache

Rex Dieter wrote:
> We had similar problems, and our best solution was to remove the 
> "AddDefaultCharset" config option altogether.  This allows individual 
> pages to specify their own encoding using meta tags:
> <meta http-equiv="Content-Type" content="text/html; charset=utf-8"> 
> and browsers to properly auto detect charsets on pages that fail to 
> explicity set them.
>
> -- Rex
> http://lists.centos.org/mailman/listinfo/centos
>   
again no luck unfortunately. The strange thing is that both Apaches are
configured the same so I would expect the same problem with both. This
not being the case, I'm thinking the problem is not with Apache but with
Horde or elsewhere. However Horde was copied from one server to another
(it's actually the original install that's giving the problem so that
rules out an error when copying across).

Thanks,
Andy.
_______________________________________________
CentOS mailing list
CentOS at centos.org
http://lists.centos.org/mailman/listinfo/centos




The contents of this communication, including any attachments, may be confidential, privileged or otherwise protected from disclosure.  They are intended solely for the use of the individual or entity to whom they are addressed.  If you are not the intended recipient, please do not read, copy, use or disclose the contents of this communication.  Please notify the sender immediately and delete the communication in its entirety.