[ https://issues.apache.org/jira/browse/SOLR-412?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12542609 ]
Hoss Man commented on SOLR-412: ------------------------------- i'm confused as to what the fix here would be... what do you think Solr should do instead of the current behavior? the XSLTResponseWriter takes the media-type and uses it as the Content-Type ... Tomcat decides that since the Content-Type doesn't have a charset, it will add one (it's default, which i'm assuming can be configured in the tomcat configs) ...what would you suggest as an improvement? (i agree UTF-8 should be the Solr default as much as possible ... but the point of the XSLTResponseWriter is to give the xslt creator total control over the content-type ... doing anything that might circumvent their intentions seems like a pad idea). > XsltWriter does not output UTF-8 by default > ------------------------------------------- > > Key: SOLR-412 > URL: https://issues.apache.org/jira/browse/SOLR-412 > Project: Solr > Issue Type: Bug > Components: search > Affects Versions: 1.2 > Environment: Tomcat 5.5 > Linux Red Hat ES4 (2.6.9-5.ELsmp from 'uname -a') > Reporter: Lance Norskog > > XsltWriter outputs XML text in ISO-8859-1 encoding by default. > Tomcat 5.5 has URIEncoding="UTF-8" set in the <Connector> element as > described in the Wiki. > This outout description in the XML: > <xsl:output method="xml" encoding="utf-8" /> > gives output with this header: > HTTP/1.1 200 OK > Server: Apache-Coyote/1.1 > Content-Type: text/xml;charset=ISO-8859-1 > Transfer-Encoding: chunked > Date: Wed, 14 Nov 2007 17:49:11 GMT > I had to change the <xsl:output> directive to this: > <xsl:output media-type="text/xml; charset=UTF-8" encoding="UTF-8"/> > This is the root cause of SOLR-233. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.