[
https://issues.apache.org/jira/browse/SOLR-443?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12606614#action_12606614
]
Yonik Seeley commented on SOLR-443:
-----------------------------------
Did you try setting URIEncoding="UTF-8" on the connector?
Without that, you can't even correctly do a query that contains international
chars.
I indexed the example data, and with standard tomcat config, verified that
SolrJ found nothing when searching for hello (with an accent over the e... it's
in solr.xml) with both GET and POST.
After editing the tomcat config and switching it to UTF-8, both GET and POST
correctly find the solr example document.
bq. a NullPointerException from the bowels of the faceting code.
That seems like a related but separate issue, and it would be nice if it were
handled more gracefully.
> 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-multipart.patch, solr-443.patch,
> solr-443.patch, SolrDispatchFilter.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.
