forrest-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From David Crossley <>
Subject Re: forrest output charset mismatch with httpd
Date Wed, 01 Feb 2006 05:59:55 GMT
Yonik Seeley wrote:
> David Crossley wrote:
> >
> > I don't think that there is anything for us to fix.
> > This is an "Appche HTTP Server" configuration issue.
> Agreed.  This isn't a forrest bug.  It might be a nice feature to be
> able to output latin-1 or ascii html though.

You can. Thorsten showed in another message.
If you want that to be across your whole forrest,
then tweak main/webapp/sitemap.xmap to set the
encoding for the html serializer.

> > Using wget i see that we have proper match betwwen HTTP headers
> > and the Content-Type heclared in the head section of our html.
> >
> > I tried temporarily adding to Cocoon's .htaccess and that
> > fixed theirs.
> >
> > Using wget against shows the same
> > as Forrest. So i don't see what the problem is.
> It works for me now too.
> Something must have changed... browser cache, server restart,
> .htaccess only read periodically?
> So Solr is OK now, but what of all the other sites?
> Here's an interesting link:

Thanks. Following through to the Bugzilla reports and to
the HTTP docs is informative.

The docs say that the default is "AddDefaultCharset Off"
but it doesn't seem so. Setting that in our .htaccess
causes the charset=ISO-8859-1 to be removed from the
http headers. From my reading that sounds like the
solution - let the client use what we have declared
in the html docs. But i am no expert.

As Thorsten suggested, sometime should gather their
facts and talk to ASF infrastructure. Perhaps the
default config is not right.


View raw message