[ https://issues.apache.org/jira/browse/SOLR-443?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ryan McKinley updated SOLR-443: ------------------------------- Attachment: solr-443.patch Andrew, does this patch work for you? rather then specify the contentType for all POST request, it only adds it for ones that don't specify it within a ContentStream > POST queries don't declare its charset > -------------------------------------- > > Key: SOLR-443 > URL: https://issues.apache.org/jira/browse/SOLR-443 > Project: Solr > Issue Type: Bug > Components: clients - java > Affects Versions: 1.2 > Environment: Tomcat 6.0.14 > Reporter: Andrew Schurman > Priority: Minor > Attachments: solr-443.patch, solr-443.patch > > > When sending a query via POST, the content-type is not set. The content > charset for the POST parameters are set, but this only appears to be used for > creating the Content-Length header in the commons library. Since a query is > encoded in UTF-8, the http headers should also specify content type charset. > On Tomcat, this causes problems when the query string contains non-ascii > characters (characters with accents and such) as it tries to parse the POST > body in its default ISO-9886-1. There appears to be no way to set/change the > default encoding for a message body on Tomcat. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.