[
https://issues.apache.org/jira/browse/SOLR-443?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12606991#action_12606991
]
Lars Kotthoff commented on SOLR-443:
------------------------------------
I can confirm that setting the content type manually to
"application/x-www-form-urlencoded; charset=UTF-8" works, but that seems like a
dirty hack to me. There's no standard/specification/.. covering that.
In any case, I'd be ok with either setting the content type manually to
something with a UTF-8 charset or putting all parameters in a multi-part POST,
albeit the first one just working because everybody happened to implement it
this way.
To be honest I'm not too happy about ignoring unknown facet values because this
*will* produce incorrect facet counts when something goes wrong. In which case
would other components add additional facet.query parameters?
> 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.
